Skip to main content
GET
Get vessel future positions
This is a paid Routing Data endpoint. See Entitlements and Paid Features for access requirements and non-entitled responses.
This endpoint requires the destination port ID (port_id) and the previous port ID (previous_port_id) for the vessel leg you want to forecast.

How to find the port IDs

If you are starting from a tracked container, call GET /v2/containers/{id}/map_geojson and inspect the port features. Each port feature includes:
  • properties.location_id - the port UUID to pass as port_id or previous_port_id
  • properties.ports_sequence - the route order
  • properties.label - route label such as POL, POD, or transshipment labels
Use the destination port’s location_id as port_id, and the preceding port’s location_id as previous_port_id.

Authorizations

Authorization
string
header
required

Use a Terminal49 API key in the Authorization header with the Token prefix.

Authorization: Token YOUR_API_KEY

Path Parameters

id
string
required

Query Parameters

port_id
string<uuid>
required

The destination port id

previous_port_id
string<uuid>
required

The previous port id

Response

OK

data
Vessel with positions model · object