{"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/4060/ship+location+and+route+monitoring+api/4877/vessel+information?imoCode=9702510' --header 'Authorization: Bearer YOUR_API_KEY'
{"status":200,"success":true,"message":"IMO Code 9251183 is valid","data":{"departure_port":"Kingston Anch., Jamaica","departure_atd":"ATD: Nov 12, 02:21 UTC (10 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 ORDER","arrival_atd":"ETA: Nov 20, 14:00","latest_port_calls":[{"port_name":"Kingston Anch., Jamaica","arrival_utc":"2024-11-11T16:50:00.000000Z","departure_utc":"2024-11-12T02:21:00.000000Z","time_in_port":"9 hours, 31 minutes"},{"port_name":"locked, ","arrival_utc":"2024-11-08T20:33:00.000000Z","departure_utc":"2024-11-10T04:51:00.000000Z","time_in_port":"1 days, 8 hours, 18 minutes"},{"port_name":"locked, ","arrival_utc":"2024-11-05T12:50:00.000000Z","departure_utc":"2024-11-06T22:55:00.000000Z","time_in_port":"1 days, 10 hours, 5 minutes"},{"port_name":"locked, ","arrival_utc":"2024-10-28T16:18:00.000000Z","departure_utc":"2024-10-29T08:35:00.000000Z","time_in_port":"16 hours, 17 minutes"},{"port_name":"locked, ","arrival_utc":"2024-10-03T09:12:00.000000Z","departure_utc":"2024-10-04T15:31:00.000000Z","time_in_port":"1 days, 6 hours, 19 minutes"}]}}
curl --location --request GET 'https://zylalabs.com/api/4060/ship+location+and+route+monitoring+api/4878/get+route?imoCode=9251183' --header 'Authorization: Bearer YOUR_API_KEY'
{"status":200,"success":true,"message":"MMSI Code 205566190 is valid","data":{"position_received":"2 m ago","vessel_local_time":"-","area":"North Sea","current_port":"ANTWERP","latitude_longitude":"--- \/ ---","navigational_status":"Under way using engine","speed_course":"","ais_source":"-","last_port_calls":[{"port":"TERNEUZEN","arrival":"2024-11-20 14:44","departure":"2024-11-20 16:57","time_in_port":"2 h"},{"port":"GENT","arrival":"2024-11-20 00:19","departure":"2024-11-20 05:31","time_in_port":"5 h"},{"port":"TERNEUZEN","arrival":"2024-11-19 19:33","departure":"2024-11-19 23:09","time_in_port":"3 h"},{"port":"ANTWERP","arrival":"2024-11-19 11:45","departure":"2024-11-19 17:28","time_in_port":"5 h"},{"port":"ANTWERP","arrival":"2024-11-03 13:57","departure":"2024-11-03 15:45","time_in_port":"1 h"},{"port":"MOERDIJK","arrival":"2024-11-02 18:16","departure":"2024-11-03 06:53","time_in_port":"12 h"},{"port":"AMSTERDAM","arrival":"2024-11-02 09:02","departure":"2024-11-02 10:22","time_in_port":"1 h"},{"port":"BEVERWIJK","arrival":"2024-11-01 00:06","departure":"2024-11-02 07:24","time_in_port":"1 d"},{"port":"AMSTERDAM","arrival":"2024-10-31 13:18","departure":"2024-10-31 23:30","time_in_port":"10 h"},{"port":"2024-11-22 12:16","arrival":"Status Changed","departure":"Under way using engineMoored","time_in_port":"51.25512 \/ 4.41012 [BE] ANTWERP"}]}}
curl --location --request GET 'https://zylalabs.com/api/4060/ship+location+and+route+monitoring+api/6116/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 Location and Route Monitoring 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 provides a comprehensive vessel tracking and management system for major seaports, delivering real-time data on vessel status and movements. It offers detailed insights into vessel position, navigational status, current port, ports of arrival and departure, and weather conditions, including temperature, wind speed, and humidity in port areas.
Using unique identifiers like IMO (International Maritime Organization number) and MMSI (Maritime Mobile Service Identity), the API tracks individual vessels, presenting a detailed view of their recent port call history, dwell times, and scheduled movements. This data is essential for optimizing port operations, improving logistics planning, 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.
The API also provides information on expected vessel arrivals at specific ports, including estimated arrival times and key vessel details such as country of registration and MMSI number. Additionally, it delivers real-time weather updates at ports, aiding in operational planning and ensuring maritime safety.
The Ship Location and Route Monitoring 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 Location and Route Monitoring 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 returns real-time location data, including latitude, longitude, and navigational status.
Key fields vary by endpoint. For "GET Route," important fields include departure port, arrival ETA, and navigation status. In "GET Current Position," key fields include current port, speed, and course. Each response is structured to provide relevant details for tracking vessels.
Response data is structured in JSON format, containing a status code, success flag, message, and a data object. The data object includes specific fields relevant to the endpoint, such as vessel details or current position, making it easy to parse and utilize.
Each endpoint requires specific parameters. For instance, "GET Vessel Information" requires an IMO number, while "GET Position by MMSI" needs an MMSI code. Users can customize requests by providing these unique 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 tracking of vessels globally.
Typical use cases include logistics planning, port operations optimization, and maritime safety enhancements. Users can track vessel movements, analyze historical data, and monitor real-time conditions to improve decision-making in maritime operations.
Users can leverage the returned data to create dashboards for real-time tracking, generate reports on vessel movements, or integrate alerts for specific events. For example, using ETA data can help in scheduling port arrivals and departures efficiently.
Data accuracy is maintained through regular updates from AIS signals and quality checks on incoming data. The API aims to provide the most current information, but users should consider factors like reporting frequency and signal reception when interpreting data.
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