The Ship Tracker API is a robust solution that empowers developers to effortlessly access comprehensive vessel information and track the real-time routes of ships using their unique IMO (International Maritime Organization) numbers. Designed to cater to applications requiring vessel tracking and monitoring functionalities, this API proves invaluable for logistics and shipping management systems, maritime tracking platforms, and related applications.
With the Ship Tracker API, developers can retrieve a wealth of information about vessels, including their current position, speed, heading, destination, and other relevant data. By leveraging the IMO number, which serves as a unique identifier for each ship, developers can access precise and accurate details about the vessel's whereabouts and its planned route.
This API serves as a reliable and efficient solution for applications that require real-time ship tracking. By integrating the Vessel Tracker API, developers can provide their users with live updates on ship locations, ensuring efficient logistics management, proactive decision-making, and improved operational efficiency. Shipping companies can monitor their fleet in real-time, optimize routes, and make informed decisions based on the latest vessel positions and routes.
Additionally, the Ship Tracker API supports historical vessel data, enabling developers to access past routes and track the movement history of ships. This feature proves useful for analyzing trends, evaluating performance, and conducting post-event analysis.
The Vessel Tracker API offers a user-friendly and well-documented interface, making integration a seamless process. Developers can easily retrieve vessel information and route tracking data by sending requests to the API endpoints, facilitating smooth integration into their applications.
The API's reliability and accuracy ensure that developers can rely on it for critical vessel tracking functionalities. With real-time data updates, developers can deliver accurate and timely information to their users, enabling effective decision-making, improved operational efficiency, and enhanced customer satisfaction.
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.
In conclusion, the Ship Tracker API is a comprehensive and efficient solution for accessing vessel information and tracking ship routes in real-time. By incorporating this API into logistics, shipping management, or maritime tracking systems, developers can enhance operational efficiency, optimize routes, and deliver timely updates to their users. With its robust features, user-friendly interface, and reliable performance, the Vessel Tracker API is a valuable tool for developers seeking to incorporate vessel tracking and monitoring capabilities into their applications.
Pass the ship's IMO number and retrieve information about the ship.
Get data like:
Get Ship Info - Endpoint Features
| Object | Description |
|---|---|
imoCode |
[Required] The Vessel's IMO code. |
{"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/2203/ship+tracker+api/2041/get+ship+info?imoCode=9270622' --header 'Authorization: Bearer YOUR_API_KEY'
This endpoint will allow you to retrieve the current route of a desired vessel.
Get:
Also, retrieve the latest ports, and how long they where in that port.
Get Ship Route - Endpoint Features
| Object | Description |
|---|---|
imoCode |
[Required] The Vessel's IMO code. |
{"status":200,"success":true,"message":"IMO Code 9251183 is valid","data":{"departure_port":"San Pedro de Macoris, Dominican Rep","departure_atd":"ATD: Jan 27, 10:58 UTC (8 days ago)","flag":null,"length_beam":"119 \/ 19 m","imo_mmsi":"9251183 \/ 538009548","navigation_status":"-","current_draught":"5.8 m","course_speed":"\u00a0","arrival_port":"Santo Domingo, Dominican Rep","arrival_atd":"ETA: Jan 29, 15:30","latest_port_calls":[{"port_name":"San Pedro de Macoris, Dominican Rep","arrival_utc":"2026-01-26T11:29:00.000000Z","departure_utc":"2026-01-27T10:58:00.000000Z","time_in_port":"23 hours, 29 minutes"},{"port_name":"locked, ","arrival_utc":"2026-01-22T18:27:00.000000Z","departure_utc":"2026-01-25T12:15:00.000000Z","time_in_port":"2 days, 17 hours, 48 minutes"},{"port_name":"locked, ","arrival_utc":"2026-01-20T11:10:00.000000Z","departure_utc":"2026-01-21T12:30:00.000000Z","time_in_port":"1 days, 1 hours, 20 minutes"},{"port_name":"locked, ","arrival_utc":"2026-01-07T21:20:00.000000Z","departure_utc":"2026-01-09T06:52:00.000000Z","time_in_port":"1 days, 9 hours, 32 minutes"},{"port_name":"locked, ","arrival_utc":"2026-01-06T18:48:00.000000Z","departure_utc":"2026-01-07T06:40:00.000000Z","time_in_port":"11 hours, 52 minutes"}]}}
curl --location --request GET 'https://zylalabs.com/api/2203/ship+tracker+api/2042/get+ship+route?imoCode=9251183' --header 'Authorization: Bearer YOUR_API_KEY'
Pass the vessel MMSI code and retrieve information about the ship.
Get data like:
Get Latest Ports by MMSI Code - Endpoint Features
| Object | Description |
|---|---|
mmsiCode |
[Required] Indicates an MMSI Code |
{"status":200,"success":true,"message":"MMSI Code 205566190 is valid","data":{"position_received":"10 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/2203/ship+tracker+api/6114/get+latest+ports+by+mmsi+code?mmsiCode=205566190' --header 'Authorization: Bearer YOUR_API_KEY'
| 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.
The Ship Tracker 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 ship data, including the ship's current position, speed, heading, destination, ETA (estimated time of arrival), and historical route information. This information enables you to track ships in real-time and analyze their past movements.
The Ship Tracker 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.
The "Get Ship Info" endpoint returns detailed information about a ship, including its IMO number, vessel name, ship type, flag, gross tonnage, summer deadweight, length overall, beam, and year of built. This data helps users understand the ship's specifications and identity.
The "Get Ship Route" endpoint includes key fields such as departure port, departure time, callsign, navigation status, current draught, course, speed, arrival port, and estimated time of arrival (ETA). This information is essential for tracking a vessel's journey.
The response from the "Get Current Position" endpoint is structured in a JSON format, containing fields like area, current port, latitude, longitude, navigational status, speed, and course. Each field provides specific details about the vessel's current status and location.
The "Get Current Position By MMSI" endpoint requires the vessel's MMSI code as a parameter. Users can retrieve data such as destination, reported ETA, speed, heading, draught, and navigational status, allowing for tailored tracking of specific vessels.
The Ship Tracker API sources its data from both terrestrial and satellite AIS (Automatic Identification System) data. This dual-source approach enhances the accuracy and reliability of the vessel tracking information provided to users.
Typical use cases include logistics management, fleet monitoring, maritime safety applications, and route optimization. Developers can use the API to provide real-time updates, analyze shipping trends, and improve operational efficiency in maritime operations.
Users can utilize the returned data to track a vessel's recent port calls, including arrival and departure times, time spent in each port, and current navigational status. This information aids in understanding a vessel's operational patterns and scheduling.
If users receive partial or empty results, they should check the input parameters for accuracy, ensure the vessel's IMO or MMSI code is valid, and consider the possibility of temporary data unavailability. Implementing error handling in their applications can also improve user experience.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
1,324ms
Service Level:
100%
Response Time:
1,289ms
Service Level:
100%
Response Time:
1,654ms
Service Level:
100%
Response Time:
2,575ms
Service Level:
100%
Response Time:
564ms
Service Level:
100%
Response Time:
360ms
Service Level:
100%
Response Time:
1,304ms
Service Level:
100%
Response Time:
97ms
Service Level:
100%
Response Time:
169ms
Service Level:
100%
Response Time:
405ms
Service Level:
100%
Response Time:
316ms
Service Level:
83%
Response Time:
339ms
Service Level:
100%
Response Time:
393ms
Service Level:
100%
Response Time:
704ms
Service Level:
100%
Response Time:
717ms
Service Level:
100%
Response Time:
381ms
Service Level:
100%
Response Time:
542ms
Service Level:
100%
Response Time:
586ms
Service Level:
100%
Response Time:
3,618ms
Service Level:
100%
Response Time:
1,015ms