Track Ship in Your Port with Datalastic API
Tracking ships individually one by one via an API is an awesome feature. But what if you want to track a certain area like a busy port or a whole water body, like a sea or a canal? Datalastic track maritime port activity API makes this possible – and fast!
What the API does essentially is to return all vessels and ships coming in and going out of a circled area that you specify in the endpoint.
You select a static point on the map or set a ship as the center point, and track the circled area around this point. You can quickly check which port is around your desired area and select a port as the center point. You select the size of the area by adding the radius. The response then returns all ships that are moving in and out of that area, allowing you to track the maritime traffic ship by ship at once.
So, you are not only receiving traffic data for one ship but ALL within the area. The response includes not only updated geo data but also many other passive details of the vessels, making the API a perfect all-in-one tool to fully track maritime traffic with ship information. We will get in more detail of the data you can find in a response below, so keep reading!
One of the major advantages of the API is that it can focus on ports. Ports are the obvious locations where vessel traffic is the busiest. Ships in ports tracking API lets you monitor all inbound and outbound vessels in the ports of your choice. Monitor complete and real-time vessel activity and maritime traffic of ports around the world with our track maritime port activity API!
Set the radius you want covered yourself! Adjust the radius based on how much field you’d like to cover.
Track Maritime Port Activity API Developer Information
You may choose either a spot on the map based on latitude/longitude, or choose a vessel based on its MMSI number and set this as the origin point. The radius value is in the nautical mile and can be 50 at maximum.
Important Tip: You can combine multiple locations to expand the area you are tracking, allowing you to track vast bodies of water at once, for example, the whole of the Black Sea. This may be necessary if you are looking to cover a wider area than a 50 NM radius at a time which is the limit per response.
Endpoint example for tracking based on a certain spot:
Endpoint example for tracking based on a vessel by MMSI number:
(The Maritime Mobile Service Identity number is unique for each vessel, allowing setting the exact vessel you want as the origin point. It typically consists of 9 digits)
Example API response:
We will get more in detail of the parameters in a standard response below. Before we do, here’s how the data of ships in ports tracking API looks like so you can visualize better:
“type_specific”: “Towing Vessel”,
“destination”: “XX XXX\u003eUS^0ZTT”,
“name”: “E W ELLEFSEN”,
API Parameters in the Response:
- radius – Radius in NM. Max 50 NM
- lat, lon – Geo-coordinates of center
- uuid – The search will be performed in a radius around the Vessel with this UUID.
- mmsi – The search will be performed in a radius around the Vessel with this MMSI.
- imo – The search will be performed in a radius around the Vessel with this IMO.
- port_uuid – The search will be performed in a radius around the Port with this UUID.
- port_unlocode – The search will be performed in a radius around the Port with this UNLOCODE.
As you can see, the response returns all ships in the area at once and includes the details of each ship one by one starting from the “UUID”, ending at the “distance” value. The API returns data in real-time, so changing details such as the latitude, longitude, speed, course, last position, etc. requires making a new API call to update. The data updates frequently, allowing you to have the latest data at all times each time you refresh it.