Entitlement overview
Vessel data access
Vessel data is part of Routing Data. These rules apply to every/v2/vessels endpoint, whether you call it with an API key or, where the endpoint allows it, a publishable API key.
A vessel counts as yours while at least one of your actively tracked shipments references it, including transshipment vessels and vessels for upcoming legs. When you stop tracking every shipment that references a vessel, its endpoints return
404 for you.
The same rules apply to vessel positions inside other responses. In included vessel resources and webhook payloads, the vessel’s position fields (latitude, longitude, nautical_speed_knots, navigational_heading_degrees, and position_timestamp) are null when your account does not have Routing Data or the vessel is not on one of your actively tracked shipments. The field names stay the same, so your parser does not need to change.
The standalone GET /v2/vessels/{id}/location endpoint has been removed. Read the current position from GET /v2/vessels/{id} instead.