Vessels
Vessel positions
Where several ships were last heard, and the ports they are in: up to 100 at once, each by its IMO number or MMSI, e.g. to show a fleet on a map. Each position is as position gives it, in the order asked; a ship with no known position is left out.
The call counts as a request for each ship asked about.
apiKeyAuthorizationBearer <token>An API key from the dashboard: a secret key (wk_sk_) from servers, or a publishable key (wk_pk_) from the origins listed on it. A workload can send its token in place of a secret key. See Authentication.
id*array<|>A ship, as imo: and its IMO number or mmsi: and its MMSI. Repeat it for each ship, up to 100: id=imo:9811000&id=mmsi:235009802.
Where the ships were last heard.
application/json- response
results*array<>curl -X GET 'https://waykite.com/api/v1/vessels/positions?id=string'{
"results": [
{
"mmsi": 563254200,
"imo": 9987196,
"at": "2026-10-26T19:41:27.369Z",
"lat": 51.903591666666664,
"lon": 3.4542516666666665,
"speed_kn": 0,
"course_deg": 276.3,
"heading_deg": 200,
"nav_status": 1,
"in_port": null
}
]
}Vessel position GET
Where a ship was last heard, and the port it is in. `at` says how fresh the position is: a ship that goes unheard keeps the position it was last heard at, and coverage depends on the region. When no position is known for the ship, the response is `204 No Content`, with an empty body.
Vessel voyage GET
Where a ship is going, and when. `destination_raw` and `reported_eta` are what its crew broadcasts. `next_port` is our estimate for passenger ships, cargo ships and tankers at sea: the port the destination most likely means, and when we expect the ship there. When no ship is known by the number, the response is `204 No Content`, with an empty body.