openapi: 3.2.0 info: title: ShipFinder Global Maritime Data 7 Event Dataset/7.1… description: Verbatim assembly of the per-endpoint OpenAPI 3.0.1 fragments ShipFinder publishes on docs.shipfinder.com (one fragment per endpoint page, indexed by the provider llms.txt). Path items are reproduced exactly as published; only the enclosing document (info/servers/tags) is API Evangelist assembly. No operation content was altered. version: 1.0.0 servers: [] tags: - name: 7 Event Dataset/7.1 Monitored Fleet Management paths: /v1/Event/AddFleet: post: summary: 7.1.1 Create Fleet deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | | `https://api.elaneglobal.com/v1/Event/AddFleet` | Post | **Example API Call** https://api.elaneglobal.com/v1/Event/AddFleet?key=1F6D701272402D1E7D8D316CCE519123&fleet_name=myfleet123&mmsis=477985700,412751690&monitor=6 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. Note: Each monitoring type selected in the monitor field requires corresponding permissions to be enabled first.If you lack the required permissions, the system will return:"You do not have access permission". If your services are already activated but the number of monitored vessels exceeds your permitted quota, the system will return:"The number of queryable vessels exceeds the limit". You may check your current permission quota in the Permission section of the dashboard. To upgrade your services or expand your vessel monitoring quota, please contact our support team.' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: [] requestBody: content: application/json: schema: type: object properties: key: type: string description: Your personal Shipfinderer API key to verify service permissions. fleet_name: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. mmsis: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. monitor: type: string description: 'Specifies the monitoring content for the fleet. 1 = Fleet Vessel Query 2 = Real-time Vessel Position Push 3 = Vessel Arrival/Departure Event Push 4 = Dynamic ETA Push 5 = AIS Abnormal Event Push 6 = Geofence Monitoring Push 7 = Vessel Alongside Event Push Separate multiple values by commas.' required: - key - fleet_name - mmsis - monitor x-apifox-orders: - key - fleet_name - mmsis - monitor - 01KMD0YYBXC401EWT6S1717M4X example: key: 1F6D701272402D1E7D8D316CCE519123 fleet_name: myfleet123 mmsis: 477985700,412751690 monitor: '6' responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data example: status: 0 msg: '' data: fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 fleet_name: 自有船队在途监控 mmsis: 412751690,477985700 monitor: '6' headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432035260-run operationId: postV1EventAddFleet x-operation-id-source: derived /v1/Event/AddVesselToFleet: post: summary: 7.1.5 Add Vessels to Fleet deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | |`https://api.elaneglobal.com/v1/Event/AddVesselToFleet` | Post | **Example API Call** https://api.elaneglobal.com/v1/Event/AddVesselToFleet?key=1F6D701272402D1E7D8D316CCE519123&fleet_id=3f2062c6-b796-4a03-b923-48628794dd86&mmsis=413983657 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. New users receive a complimentary usage quota upon API key creation. **Note:** When adding vessels to a fleet, the system will validate your vessel monitoring quota. If the total number of vessels exceeds your permitted limit, the system will return the error: "The number of vessels exceeds the permission limit." You may add an unlimited number of vessels to a fleet that has no monitoring permissions bound (this option is available when creating fleets via the dashboard). However, such fleets will not support any query or monitoring functions. The same quota validation will apply if you bind monitoring permissions to this fleet at a later stage, and the same over-limit error will be triggered if applicable. |' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: [] requestBody: content: application/json: schema: type: object properties: key: type: string description: Your personal Shipfinderer API key to verify service permissions fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. mmsis: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. This is an incremental update that does not modify existing vessels in the fleet.Duplicate MMSI numbers will be ignored and not added again. required: - key - fleet_id - mmsis x-apifox-orders: - key - fleet_id - mmsis example: key: 1F6D701272402D1E7D8D316CCE519123 fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 mmsis: '413983657' responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data example: status: 0 msg: '' data: fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 fleet_name: myfleet123 mmsis: 412751690,413983657,477985700 monitor: '6' headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432100231-run operationId: postV1EventAddVesselToFleet x-operation-id-source: derived /v1/Event/DeleteFleet: post: summary: 7.1.4 Delete Fleet deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | |`https://api.elaneglobal.com/v1/Event/DeleteFleet` | Post | **Example API Call** https://api.elaneglobal.com/v1/Event/DeleteFleet?key=1F6D701272402D1E7D8D316CCE519123&fleet_id=3f2062c6-b796-4a03-b923-48628794dd86 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. New users receive a complimentary usage quota upon API key creation. **Note:** After a fleet is deleted, all related push services will stop including data from this fleet, including: fleet vessel queries, real-time position push, arrival/departure event push, ETA push, and AIS event push. If no other fleets remain bound to the push service, no further messages will be pushed. The geofence alert push follows a different logic: if the bound fleet is deleted, the system will push alerts for all vessels entering or exiting the geofence. To modify geofence alerts, you must bind a new fleet or set new filters. To disable geofence alerts entirely, you must delete the geofence.' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: - name: key in: query description: Your personal Shipfinderer API key to verify service permissions required: true example: 1F6D701272402D1E7D8D316CCE519123 schema: type: string - name: fleet_id in: query description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. required: true example: 3f2062c6-b796-4a03-b923-48628794dd86 schema: type: string responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data example: status: 0 msg: '' data: fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 fleet_name: 自有船队在途监控 mmsis: 413983657,412751690 monitor: '6' headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432076110-run operationId: postV1EventDeleteFleet x-operation-id-source: derived /v1/Event/DeleteFleetVessel: post: summary: 7.1.7 Remove Vessels from Fleet deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | | https://api.elaneglobal.com/v1/Event/DeleteFleetVessel | Post | **Example API Call** https://api.elaneglobal.com/v1/Event/DeleteFleetVessel?key=1F6D701272402D1E7D8D316CCE519123&fleet_id=3f2062c6-b796-4a03-b923-48628794dd86&mmsis=413461440 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. New users receive a complimentary usage quota upon API key creation.' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: [] requestBody: content: application/json: schema: type: object properties: key: type: string description: Your personal Shipfinderer API key to verify service permissions fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. mmsis: type: string description: Add vessels to the fleet. Enter vessel MMSI numbers separated by commas. Removes one or more vessels from the fleet. Only vessels already present in the fleet will be deleted; invalid or non-existent MMSIs will not affect other vessels. required: - key - fleet_id - mmsis x-apifox-orders: - key - fleet_id - mmsis example: key: 1F6D701272402D1E7D8D316CCE519123 fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 mmsis: '413461440' responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data example: status: 0 msg: '' data: fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 fleet_name: 自有船队在途监控 mmsis: 413983657,412751690 monitor: '6' headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432106004-run operationId: postV1EventDeleteFleetVessel x-operation-id-source: derived /v1/Event/GetFleet: get: summary: 7.1.3 Query Fleet deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | | `https://api.elaneglobal.com/v1/Event/GetFleet` | Get | **Example API Call** https://api.elaneglobal.com/v1/Event/GetFleet?key=1F6D701272402D1E7D8D316CCE519123&fleet_id=3f2062c6-b796-4a03-b923-48628794dd86 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. New users receive a complimentary usage quota upon API key creation.' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: - name: key in: query description: '' required: true example: 1F6D701272402D1E7D8D316CCE519123 schema: type: string - name: fleet_id in: query description: '' required: true example: 3f2062c6-b796-4a03-b923-48628794dd86 schema: type: string responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432057101-run operationId: getV1EventGetFleet x-operation-id-source: derived /v1/Event/UpdateFleetInfo: post: summary: 7.1.2 Update Fleet Information deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | | `https://api.elaneglobal.com/v1/Event/UpdateFleetInfo` | Post | **Example API Call** https://api.elaneglobal.com/v1/Event/UpdateFleetInfo?key=1F6D701272402D1E7D8D316CCE519123&fleet_id=3f2062c6-b796-4a03-b923-48628794dd86&mmsis=477985700&monitor=5 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. New users receive a complimentary usage quota upon API key creation. Note: When updating fleet information, the submitted data will overwrite the existing records entirely, not incrementally. Please use this operation with caution, especially for the vessel list and monitoring content.' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: [] requestBody: content: application/json: schema: type: object properties: key: type: string description: Your personal Shipfinderer API key to verify service permissions fleet_id: type: string description: Your personal Shipfinderer API key to verify service permissions mmsis: type: string description: Batch Update of Fleet Vessels. Enter vessel MMSI numbers separated by commas. This is a full overwrite update with no incremental addition or removal of individual vessels. monitor: type: string description: 'Update monitoring content for the fleet. 1 = Fleet Vessel Query 2 = Real-time Vessel Position Push 3 = Vessel Arrival/Departure Event Push 4 = Dynamic ETA Push 5 = AIS Abnormal Event Push 6 = Geofence Monitoring Push 7 = Vessel Alongside Event Push Separate multiple values by commas. This is a full overwrite update; no incremental addition or removal is performed.' fleet_name: type: string description: Enter a name to update the fleet name. required: - key - fleet_id - mmsis - monitor - fleet_name x-apifox-orders: - key - fleet_id - mmsis - monitor - fleet_name example: key: 1F6D701272402D1E7D8D316CCE519123 fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 mmsis: '477985700' monitor: '5' responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data example: status: 0 msg: '' data: fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 fleet_name: 自有船队在途监控 mmsis: 412751690,477985700 monitor: '4' headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432048484-run operationId: postV1EventUpdateFleetInfo x-operation-id-source: derived /v1/Event/UpdateFleetVessel: post: summary: 7.1.6 Batch Update Vessels in Fleet deprecated: false description: '**Endpoint** | Endpoint | HTTP Method | | --- | --- | | `https://api.elaneglobal.com/v1/Event/UpdateFleetVessel` | Post | **Example API Call** https://api.elaneglobal.com/v1/Event/UpdateFleetVessel?key=1F6D701272402D1E7D8D316CCE519123&fleet_id=3f2062c6-b796-4a03-b923-48628794dd86&mmsis=413461440,412751690,413983657 **Note:** - The key `1F6D701272402D1E7D8D316CCE519123` is the official key of Shipfinder.com, bound to the domain api.shipfinder.com. - Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain. - To trial the service, please create your own key in the Dashboard. New users receive a complimentary usage quota upon API key creation.' tags: - 7 Event Dataset/7.1 Monitored Fleet Management parameters: [] requestBody: content: application/json: schema: type: object properties: key: type: string description: Your personal Shipfinderer API key to verify service permissions fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. mmsis: type: string description: Add vessels to the fleet. Enter vessel MMSI numbers separated by commas. This is a full overwrite update with no incremental addition or removal of individual vessels. required: - key - fleet_id - mmsis x-apifox-orders: - key - fleet_id - mmsis example: key: 1F6D701272402D1E7D8D316CCE519123 fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 mmsis: 413461440,412751690,413983657 responses: '0': description: '' content: application/json: schema: type: object properties: status: type: integer msg: type: string data: type: object properties: fleet_id: type: string description: Unique identifier for the fleet, used for subsequent maintenance of fleet information. fleet_name: type: string description: Add vessels to the fleet. Enter multiple MMSI numbers separated by commas. mmsis: type: string description: Vessels MMSIs to be managed under the fleet. monitor: type: string description: Monitored content associated with the fleet; can be modified via the Update Fleet Information API or the Dashboard. required: - fleet_id - fleet_name - mmsis - monitor x-apifox-orders: - fleet_id - fleet_name - mmsis - monitor required: - status - msg - data x-apifox-orders: - status - msg - data example: status: 0 msg: '' data: fleet_id: 3f2062c6-b796-4a03-b923-48628794dd86 fleet_name: myfleet123 mmsis: 413983657,413461440,412751690 monitor: '6' headers: {} x-apifox-name: success security: [] x-apifox-folder: 7 Event Dataset/7.1 Monitored Fleet Management x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/7948067/apis/api-432080706-run operationId: postV1EventUpdateFleetVessel x-operation-id-source: derived x-evidence: harvested: '2026-08-09' index: https://docs.shipfinder.com/llms.txt index_http_status: 200 fragments: 40 note: Each path item was extracted verbatim from the "## OpenAPI Specification" yaml block on the corresponding docs page. The provider publishes no consolidated OpenAPI document. sources: - path: /v1/AIS/FleetPosition method: GET title: 1.1.3 Fleet Position source: https://docs.shipfinder.com/430293359e0.md - path: /v1/AIS/VesselFlagInfo method: GET title: 1.5 Vessel Flag Information source: https://docs.shipfinder.com/429919472e0.md - path: /v1/AIS/VesselPositionMulti method: GET title: 1.1.2 Multi-vessel Position source: https://docs.shipfinder.com/430292321e0.md - path: /v1/AIS/VesselPositionSingle method: GET title: 1.1.1 Single Vessel Position source: https://docs.shipfinder.com/428990613e0.md - path: /v1/AIS/VesselSearch method: GET title: 1.2 Vessel Search source: https://docs.shipfinder.com/428749512e0.md - path: /v1/AIS/VesselsInZone method: GET title: 1.4 Vessels in Zone source: https://docs.shipfinder.com/429583708e0.md - path: /v1/AIS/VesselsNearby method: GET title: 1.3 Vessels Nearby source: https://docs.shipfinder.com/429003024e0.md - path: /v1/Event/AddFleet method: POST title: 7.1.1 Create Fleet source: https://docs.shipfinder.com/432035260e0.md - path: /v1/Event/AddGeofence method: POST title: 7.2.1 Geofence Creation source: https://docs.shipfinder.com/433382008e0.md - path: /v1/Event/AddVesselSpeedAlert method: POST title: 7.3.1 Add Vessel Speed Alert Subscription source: https://docs.shipfinder.com/433460139e0.md - path: /v1/Event/AddVesselToFleet method: POST title: 7.1.5 Add Vessels to Fleet source: https://docs.shipfinder.com/432100231e0.md - path: /v1/Event/DeleteFleet method: POST title: 7.1.4 Delete Fleet source: https://docs.shipfinder.com/432076110e0.md - path: /v1/Event/DeleteFleetVessel method: POST title: 7.1.7 Remove Vessels from Fleet source: https://docs.shipfinder.com/432106004e0.md - path: /v1/Event/DeleteGeofence method: DELETE title: 7.2.4 Geofence Deletion source: https://docs.shipfinder.com/433422419e0.md - path: /v1/Event/DeleteVesselSpeedAlert method: POST title: 7.3.2 Delete Vessel Speed Alert Subscription source: https://docs.shipfinder.com/433471968e0.md - path: /v1/Event/GetFleet method: GET title: 7.1.3 Query Fleet source: https://docs.shipfinder.com/432057101e0.md - path: /v1/Event/GetGeofence method: GET title: 7.2.3 Geofence Query source: https://docs.shipfinder.com/433414777e0.md - path: /v1/Event/UpdateFleetInfo method: POST title: 7.1.2 Update Fleet Information source: https://docs.shipfinder.com/432048484e0.md - path: /v1/Event/UpdateFleetVessel method: POST title: 7.1.6 Batch Update Vessels in Fleet source: https://docs.shipfinder.com/432080706e0.md - path: /v1/Event/UpdateGeofence method: POST title: 7.2.2 Geofence Update source: https://docs.shipfinder.com/433396710e0.md - path: /v1/Event/VesselSpeedAlertList method: GET title: 7.3.3 Query Vessel Speed Alert Subscription List source: https://docs.shipfinder.com/433473614e0.md - path: /v1/History/PortCallRecordsByPort method: GET title: 3.6 Port Calls Records for Port source: https://docs.shipfinder.com/430531632e0.md - path: /v1/History/PortCallRecordsByVessel method: GET title: 3.3 Vessel Port Call History source: https://docs.shipfinder.com/430426234e0.md - path: /v1/History/PortCallRecordsByVesselAtPort method: GET title: 3.4 Vessel Port Call Records at Specific Port source: https://docs.shipfinder.com/430484162e0.md - path: /v1/History/VesselCurrentPortCall method: GET title: 3.5 Vessel Current Port Call source: https://docs.shipfinder.com/430498718e0.md - path: /v1/History/VesselHistoryTrack method: GET title: 3.1 Vessel History Track source: https://docs.shipfinder.com/430346103e0.md - path: /v1/History/VesselStsEvents method: GET title: 3.2 Ship-to-Ship (STS) Events source: https://docs.shipfinder.com/430352093e0.md - path: /v1/Meteorology/CycloneInfo method: GET title: 5.1.2 Tropical Cyclone Details by Point source: https://docs.shipfinder.com/431698143e0.md - path: /v1/Meteorology/CyclonesList method: GET title: 5.1.1 Global Tropical Cyclones List source: https://docs.shipfinder.com/431698053e0.md - path: /v1/Meteorology/MarineWeather method: GET title: 5.3 Global Marine Weather source: https://docs.shipfinder.com/431272522e0.md - path: /v1/Meteorology/TideStationInfo method: GET title: 5.2.2 Query Single Tide Gauge Station Details source: https://docs.shipfinder.com/431865286e0.md - path: /v1/Meteorology/TideStationList method: GET title: 5.2.1 Request parameters for Global Tide Gauge Stations List source: https://docs.shipfinder.com/431857907e0.md - path: /v1/Prediction/ETA method: GET title: 4.3 ETA Query source: https://docs.shipfinder.com/431244206e0.md - path: /v1/Prediction/RoutePlanPointToPoint method: GET title: 4.1 Point-to-Point Route Planning source: https://docs.shipfinder.com/431124483e0.md - path: /v1/Prediction/RoutePlanPortToPort method: GET title: 4.2 Port-to-Port Route Planning source: https://docs.shipfinder.com/431244012e0.md - path: /v1/Voyage/PortAnchoredVessels method: GET title: 2.3 Currently Anchored Vessels source: https://docs.shipfinder.com/430236145e0.md - path: /v1/Voyage/PortBerthedVessels method: GET title: 2.2 Currently Berthed Vessels source: https://docs.shipfinder.com/430197412e0.md - path: /v1/Voyage/PortExpectedArrivals method: GET title: 2.4 Inbound / Expected Arrivals source: https://docs.shipfinder.com/430249182e0.md - path: /v1/Voyage/PortInfo method: GET title: 2.1 Port Information source: https://docs.shipfinder.com/429932201e0.md - path: /v1/Warning/NavigationalWarnings method: GET title: 6.1 China Region Navigational Warnings source: https://docs.shipfinder.com/431872073e0.md