Ship Locator API

The Ship Locator API grants users detailed, up-to-the-minute information on the whereabouts and course of any vessel through its IMO number.

About the API: 

The Ship Locator API serves as a crucial tool for accessing data and monitoring any vessel's real-time trajectory using its IMO number. This API proves especially beneficial for constructing applications that demand vessel tracking or monitoring features, such as logistics or ship management systems.

Moreover, users gain access to up-to-the-minute tracking details, including the vessel's current route, last port, and estimated arrival and departure times. This dynamic dataset simplifies vessel tracking across various ports and routes, facilitating real-time monitoring of vessel movements.

Renowned for its reliability and efficiency, the Ship Locator API guarantees swift response times and constant availability. Thoroughly tested to handle significant request volumes, it stands as the preferred choice for applications requiring prompt and accurate vessel tracking data.

A notable aspect of this API is its scalability, accommodating a wide array of vessel types, from freighters to cruise ships. This flexibility enables users to customize the retrieved data to suit their specific requirements, facilitating the creation of ship tracking functionalities tailored to the application's needs.

In conclusion, the Ship Locator API proves indispensable for users developing applications necessitating vessel tracking or monitoring features. Whether designing a logistics system, a ship management application, or a ship tracking platform, this API streamlines the delivery of fast and accurate ship tracking data, thereby enhancing ship management and operational efficiency.

 

What this API receives and what your API provides (input/output)?

Just with the Vessel IMO number you will be available to retrieve relevant information about the ship. Name, flag, tonnage, and more. 

Also, you will be able to retrieve the current route. Where are they going? Where did they just depart from? Where did they be in the past few days? When they are supposed to arrive? Get all this information with this API. 

 

What are the most common uses cases of this API?

  1. Logistics and shipping management: Logistics and shipping companies can use the API to track the movements of their vessels in real time. The API can help companies optimize their supply chain operations and improve delivery times by providing accurate vessel tracking data.

  2. Port authorities: Port authorities can use the API to monitor vessel movements within their ports. The API can help port authorities improve safety, security, and traffic management by providing up-to-date vessel tracking information.

  3. Insurance companies: Insurance companies can use the API to monitor vessel movements and assess risk levels. The API can help insurance companies better understand the risks associated with different vessels and routes, allowing them to make more informed underwriting decisions.

  4. Maritime law enforcement: Maritime law enforcement agencies can use the API to track vessels suspected of illegal activity. The API can help law enforcement agencies locate and apprehend vessels that are engaged in piracy, smuggling, or other illegal activities.

  5. Environmental monitoring: Environmental organizations can use the API to track vessel movements and monitor the impact of shipping on the environment. The API can help environmental organizations identify areas where shipping activity is having a negative impact on the environment, allowing them to take action to protect the environment.

 

Are there any limitations to your plans?

Besides the number of API calls, there is no other limitation

API Documentation

Endpoints


Pass the vessel IMO number and retrieve information about the ship. 

Get data like:

  • IMO number
  • Vessel Name
  • Ship type
  • Flag
  • Gross Tonnage
  • Summer Deadweight (t)
  • Length Overall (m)
  • Beam (m)
  • Year of Built


                                                                            
GET https://zylalabs.com/api/4072/ship+locator+api/4905/vessel+information
                                                                            
                                                                        

Vessel Information - Endpoint Features

Object Description
imoCode [Required] The Vessel's IMO code.
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"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"}}
                                                                                                                                                                                                                    
                                                                                                    

Vessel Information - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4072/ship+locator+api/4905/vessel+information?imoCode=9270622' --header 'Authorization: Bearer YOUR_API_KEY' 


    

This endpoint will allow you to retrieve the current route of a desired vessel. 

Get:

  • Departure Port
  • Departure ATD
  • Callsign
  • Flag
  • Length / Beam
  • IMO / MMSI
  • Navigation Status
  • Current Draught
  • Course / Speed
  • Arrival Port
  • Arrival ETA

Also, retrieve the latest ports, and how long they where in that port. 



                                                                            
GET https://zylalabs.com/api/4072/ship+locator+api/4906/get+route
                                                                            
                                                                        

Get Route - Endpoint Features

Object Description
imoCode [Required] The Vessel's IMO code.
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status":200,"success":true,"message":"IMO Code 9649225 is valid","data":{"departure_port":"Trieste, Italy","departure_atd":"ATD: Dec 5, 05:35 UTC (10 days ago)","callsign":"2HER5","flag":"United Kingdom (UK)","length_beam":"257 \/ 43 m","imo_mmsi":"9649225 \/ 235103057","navigation_status":"Under way","current_draught":"9.0 m","course_speed":"\u00a0","arrival_port":"Teesport, United Kingdom (UK)","arrival_atd":"ETA: Dec 21, 08:00","latest_port_calls":[{"port_name":"Trieste, Italy","arrival_utc":"2024-12-04T04:46:00.000000Z","departure_utc":"2024-12-05T05:35:00.000000Z","time_in_port":"1 days, 49 minutes"},{"port_name":"locked, ","arrival_utc":"2024-12-02T20:11:00.000000Z","departure_utc":"2024-12-04T03:42:00.000000Z","time_in_port":"1 days, 7 hours, 31 minutes"},{"port_name":"locked, ","arrival_utc":"2024-11-27T20:27:00.000000Z","departure_utc":"2024-11-28T08:59:00.000000Z","time_in_port":"12 hours, 32 minutes"},{"port_name":"locked, ","arrival_utc":"2024-11-25T12:42:00.000000Z","departure_utc":"2024-11-25T16:06:00.000000Z","time_in_port":"3 hours, 24 minutes"},{"port_name":"locked, ","arrival_utc":"2024-11-24T08:34:00.000000Z","departure_utc":"2024-11-25T12:41:00.000000Z","time_in_port":"1 days, 4 hours, 7 minutes"}]}}
                                                                                                                                                                                                                    
                                                                                                    

Get Route - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4072/ship+locator+api/4906/get+route?imoCode=9251183' --header 'Authorization: Bearer YOUR_API_KEY' 


    

This endpoint will allow you to retrieve the current position of the vessel. 

Get:

  • Area
  • Current Port
  • Latitude
  • Longitude
  • Navigational Status
  • Speed
  • Course
  • AIS Source


                                                                            
GET https://zylalabs.com/api/4072/ship+locator+api/4907/current+position
                                                                            
                                                                        

Current Position - Endpoint Features

Object Description
imoCode [Required] The Vessel's IMO code.
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status":200,"success":true,"message":"IMO Code 9270622 is valid","data":{"position_received":"2023-10-13 10:36","vessel_local_time":"-","area":"Gulf of Guinea","current_port":"ABIDJAN","latitude_longitude":"--- \/ ---","navigational_status":"Under way using engine","speed_course":"7.9 Knots","ais_source":"-"}}
                                                                                                                                                                                                                    
                                                                                                    

Current Position - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4072/ship+locator+api/4907/current+position?imoCode=9270622' --header 'Authorization: Bearer YOUR_API_KEY' 


    

This endpoint will allow you to retrieve the current position of the vessel based on its MMSI. 

Get:

  • Destination.
  • Reported ETA. 
  • Speed. 
  • Heading. 
  • Draught.
  • Position Received.
  • Latitude / Longitude. 
  • Navigational status.


                                                                            
GET https://zylalabs.com/api/4072/ship+locator+api/4908/get+position+by+mmsi
                                                                            
                                                                        

Get Position by MMSI - Endpoint Features

Object Description
mmsiCode [Required] The Vessel's MMSI code.
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status":200,"success":true,"message":"MMSI Code 577472000 is valid","data":{"destination":"FORCADOS TERMINAL","reported_eta":"ETA: Dec 8, 08:00","speed":"7.9 Knots","heading":null,"draught":"5.5 m","position_received":"2023-10-13 10:36","latitude_longitude":"--- \/ ---","navigational_status":"-"}}
                                                                                                                                                                                                                    
                                                                                                    

Get Position by MMSI - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4072/ship+locator+api/4908/get+position+by+mmsi?mmsiCode=577472000' --header 'Authorization: Bearer YOUR_API_KEY' 


    

Pass the vessel MMSI code and retrieve information about the ship. 

Get data like:

  • Position Received
  • Area
  • Current Port
  • Coordinates
  • Navigational status
  • Last port calls
  • arrival
  • Departure
  • Time in port


                                                                            
GET https://zylalabs.com/api/4072/ship+locator+api/6118/get+latest+ports+by+mmsi+code
                                                                            
                                                                        

Get Latest Ports by MMSI Code - Endpoint Features

Object Description
mmsiCode [Required] Indicates an MMSI Code
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status":200,"success":true,"message":"MMSI Code 205566190 is valid","data":{"position_received":"3 m ago","vessel_local_time":"-","area":"North Sea","current_port":"GENT","latitude_longitude":"--- \/ ---","navigational_status":"Moored","speed_course":"","ais_source":"-","last_port_calls":[{"port":"TERNEUZEN","arrival":"2024-12-07 12:05","departure":"2024-12-07 13:07","time_in_port":"1 h"},{"port":"ANTWERP","arrival":"2024-12-03 23:41","departure":"2024-12-04 13:27","time_in_port":"13 h"},{"port":"TERNEUZEN","arrival":"2024-12-03 18:06","departure":"2024-12-03 21:19","time_in_port":"3 h"},{"port":"GENT","arrival":"2024-12-03 07:07","departure":"2024-12-03 16:46","time_in_port":"9 h"},{"port":"TERNEUZEN","arrival":"2024-12-03 04:30","departure":"2024-12-03 06:04","time_in_port":"1 h"},{"port":"ANTWERP","arrival":"2024-11-29 15:52","departure":"2024-11-29 19:36","time_in_port":"3 h"},{"port":"BOTLEK - ROTTERDAM","arrival":"2024-11-28 05:10","departure":"2024-11-29 07:02","time_in_port":"1 d"},{"port":"SCHIEDAM","arrival":"2024-11-27 14:30","departure":"2024-11-28 04:35","time_in_port":"14 h"},{"port":"ANTWERP","arrival":"2024-11-26 18:02","departure":"2024-11-26 21:07","time_in_port":"3 h"},{"port":"2024-12-11 11:15","arrival":"Status Changed","departure":"MooredDefault","time_in_port":"51.14610 \/ 3.79635 [BE] GENT"}]}}
                                                                                                                                                                                                                    
                                                                                                    

Get Latest Ports by MMSI Code - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4072/ship+locator+api/6118/get+latest+ports+by+mmsi+code?mmsiCode=205566190' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

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 Locator API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

The Ship Locator 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 Locator 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.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the β€˜X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
100%
 Response Time
3,359ms

Category:


Related APIs