Esc
GETAPI key
Container fleet positions
GETapi.navo24.com/v1/vessel/fleet
Last known position of every tracked container ship: [imo, name, lat, lng, heading_deg, speed_knots, position_fix_at]. Refreshed in the background. Two rows shown.
Response schema
3 fields
Derived from the example response, nested as the JSON is.
data
The payload. Everything an endpoint returns sits under this key.
at
vessels
Errors
A failure carries { "ok": false, "error": { "code", "message", "severity" } }. Branch on the code, and log the message.
missing_key
No key in Authorization or x-api-key.
invalid_key
The key is unknown or revoked.
rate_limited
More than 40 requests in one minute from one client.
curl 'https://api.navo24.com/v1/vessel/fleet' \
-H "Authorization: Bearer tmcp_YOUR_API_KEY"const res = await fetch("https://api.navo24.com/v1/vessel/fleet", {
headers: {
"Authorization": "Bearer tmcp_YOUR_API_KEY"
}
});
const data = await res.json();import requests
res = requests.get(
"https://api.navo24.com/v1/vessel/fleet",
headers={"Authorization": "Bearer tmcp_YOUR_API_KEY"},
)
data = res.json()Response
{
"data": {
"at": 1793558425.5426428,
"vessels": [
[
"9320403",
"MSC LORENA",
34.6609,
129.2053,
269,
1.2,
"2026-11-02T06:37:06+00:00"
],
[
"9214214",
"GSL ARCADIA",
26.4358,
121.5589,
3,
19,
"2026-11-02T04:11:16+00:00"
]
]
}
}