{"status":200,"success":true,"message":"IMO Code 9270622 is valid","data":{"imo_number":"9270622","vessel_name":"AQUAMAN","ship_type":"Offshore Tug\/Supply Ship","flag":"Vanuatu","gross_tonnage":"2332","summer_deadweight_t":"2162","length_overall_m":"69","beam_m":"16","year_of_built":"2003"}}
curl --location --request GET 'https://zylalabs.com/api/4071/ship+positioning+and+voyage+tracking+api/4901/vessel+information?imoCode=9702510' --header 'Authorization: Bearer YOUR_API_KEY'
{"status":200,"success":true,"message":"IMO Code 9251183 is valid","data":{"departure_port":"Saint George, Bermuda","departure_atd":"ATD: May 13, 21:21 UTC (44 days ago)","callsign":"V7A4876","flag":"Marshall Islands","length_beam":"119 \/ 19 m","imo_mmsi":"9251183 \/ 538009548","navigation_status":"-","current_draught":"5.1 m","course_speed":"\u00a0","arrival_port":"FOR ORDERS","arrival_atd":"ETA: Jun 30, 00:00","latest_port_calls":[{"port_name":"Saint George, Bermuda","arrival_utc":"2024-05-13T10:41:00.000000Z","departure_utc":"2024-05-13T21:21:00.000000Z","time_in_port":"10 hours, 40 minutes"},{"port_name":"locked, ","arrival_utc":"2024-05-03T14:33:00.000000Z","departure_utc":"2024-05-04T14:16:00.000000Z","time_in_port":"23 hours, 43 minutes"}]}}
curl --location --request GET 'https://zylalabs.com/api/4071/ship+positioning+and+voyage+tracking+api/4902/get+route?imoCode=9251183' --header 'Authorization: Bearer YOUR_API_KEY'
{"status":200,"success":true,"message":"MMSI Code 205566190 is valid","data":{"position_received":"15 m ago","vessel_local_time":"-","area":"North Sea","current_port":"PUURS ZEEKANAAL BRUS","latitude_longitude":"51.11120\u00b0 \/ 4.29875\u00b0","navigational_status":"Moored","speed_course":"","ais_source":"-","last_port_calls":[{"port":"ANTWERP","arrival":"2024-08-04 10:23","departure":"2024-08-04 14:09","time_in_port":"3 h"},{"port":"THOLEN","arrival":"2024-08-03 11:21","departure":"2024-08-04 08:48","time_in_port":"21 h"},{"port":"BOTLEK - ROTTERDAM","arrival":"2024-07-30 15:45","departure":"2024-08-01 11:46","time_in_port":"1 d"},{"port":"AMSTERDAM","arrival":"2024-07-27 15:52","departure":"2024-07-30 06:58","time_in_port":"2 d"},{"port":"NIEUWEGEIN","arrival":"2024-07-27 09:38","departure":"2024-07-27 11:06","time_in_port":"1 h"},{"port":"HANSWEERT","arrival":"2024-07-26 14:28","departure":"2024-07-26 14:42","time_in_port":"13 m"},{"port":"SLUISKIL","arrival":"2024-07-25 20:38","departure":"2024-07-26 10:41","time_in_port":"14 h"},{"port":"ANTWERP","arrival":"2024-07-25 14:09","departure":"2024-07-25 16:38","time_in_port":"2 h"},{"port":"THOLEN","arrival":"2024-07-19 15:32","departure":"2024-07-25 10:56","time_in_port":"5 d"},{"port":"KEIZERSVEER","arrival":"2024-07-19 09:42","departure":"2024-07-19 10:17","time_in_port":"35 m"}]}}
curl --location --request GET 'https://zylalabs.com/api/4071/ship+positioning+and+voyage+tracking+api/6117/get+latest+ports+by+mmsi+code?mmsiCode=258785000' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Ship Positioning and Voyage Tracking API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
This API offers an advanced vessel tracking and management system for major seaports, delivering real-time data on vessel status and movements. It provides detailed insights into vessel position, navigational status, current port, ports of arrival and departure, and port-specific weather conditions, including temperature, wind speed, and humidity.
By utilizing unique identifiers such as IMO (International Maritime Organization number) and MMSI (Maritime Mobile Service Identity), the API enables precise vessel tracking, offering a comprehensive view of recent port calls, dwell times, and scheduled movements. This data is essential for optimizing port operations, streamlining logistics, and enhancing navigational safety.
The API provides real-time position of vessels using AIS data, including latitude, longitude, heading, speed, navigation status, destination and ETA. The information comes from terrestrial or satellite sources to provide global coverage and accuracy in maritime tracking.
Additionally, the API includes information on expected vessel arrivals at specific ports, providing estimated arrival times and key vessel details, including country of registration and MMSI number. It also delivers real-time weather updates for ports, supporting efficient operational planning and maritime safety.
The Ship Positioning and Voyage Tracking API is a service that allows developers to access real-time ship information and track the routes of ships using their unique IMO numbers. It provides comprehensive data about ship positions, speeds, headings, destinations, and more.
The API provides a wealth of vessel data such as course, destination, estimated time of arrival (ETA) and historical information about their routes. This information allows vessels to be tracked in real time and their past movements to be analyzed.
The Ship Positioning and Voyage Tracking API strives to provide accurate and up-to-date ship tracking data. However, please note that ship positions and other data are subject to various factors such as ship reporting frequency, reception quality, and data source reliability.
The API itself does not provide native alert or notification functionality. However, developers can leverage the data retrieved from the API to implement custom alert systems within their applications, triggering notifications based on specific ship criteria or events.
Integration is straightforward. The API offers well-documented endpoints and provides developers with clear instructions on how to make requests and retrieve ship information. Detailed documentation and code examples facilitate easy integration.
Each endpoint returns specific vessel-related data. For example, the "GET Vessel Information" endpoint provides details like IMO number, vessel name, and gross tonnage, while the "GET Current Position" endpoint offers real-time location data, including latitude, longitude, and navigational status.
Key fields vary by endpoint. For "GET Vessel Information," important fields include "vessel_name" and "gross_tonnage." In "GET Current Position," critical fields include "latitude," "longitude," and "navigational_status," which provide essential tracking information.
The response data is structured in JSON format, containing a "status," "success," "message," and a "data" object. The "data" object holds specific vessel information, such as position, route, or vessel details, making it easy to parse and utilize in applications.
Each endpoint requires specific parameters. For instance, "GET Vessel Information" needs an IMO number, while "GET Get Route" requires the vessel's IMO or MMSI. Users can customize requests by providing these identifiers to retrieve targeted data.
The API sources its data from AIS (Automatic Identification System) signals, which can be terrestrial or satellite-based. This dual-source approach enhances coverage and accuracy, allowing for reliable vessel tracking across various regions.
Typical use cases include maritime logistics optimization, real-time vessel tracking for safety, and operational planning for ports. Businesses can analyze vessel movements to improve scheduling and resource allocation based on accurate arrival and departure data.
Users can leverage the returned data to create dashboards for monitoring vessel movements, generate reports on port calls, or develop alert systems for specific navigational statuses. The structured JSON format allows for easy integration into various applications.
Data accuracy is maintained through regular updates from AIS signals and quality checks on the received data. The API aims to provide real-time information, but users should consider factors like signal reception and reporting frequency that may affect accuracy.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund