Developer portal
Freight intelligence your software can call directly.
One reference in; status, route, milestones, schedules, rates and load plans out. Every product speaks REST, and most speak MCP as well, behind a single bearer key.
Your first call
Track a container in one request.
The public lookup needs no account. Paste a container number, a bill of lading or a booking, and read back a normalised status and a truthful ETA.
See the endpointcurl -X POST 'https://api.trackingmcp.com/v1/track/public' \
-H "Content-Type: application/json" \
-d '{"reference":"MEDU1234562"}'const res = await fetch("https://api.trackingmcp.com/v1/track/public", {
method: "POST",
headers: {
"Content-Type": "application/json"
},
body: JSON.stringify({
"reference": "MEDU1234562"
})
});
const data = await res.json();import requests
res = requests.post(
"https://api.trackingmcp.com/v1/track/public",
json={
"reference": "MEDU1234562"
},
)
data = res.json() Get started in three steps.
- Make a call with no account The public container lookup needs no key. It is rate-limited per IP and meant for a quick check. Getting started
- Get an API key Sign up, mint a key in the developer settings, and send it as a bearer token on every authed request. Authentication
- Connect an MCP client Point Claude, Cursor or any MCP client at a Navo24 server and let the model call freight tools. MCP quickstart
The APIs
Browse the referenceTrackingMCP
Where every container is, and when it will really arrive.
REST MCP 17 endpoints · 7 tools api.aircargomcp.comAirCargoMCP
Any air waybill, from acceptance to delivery, on one timeline.
REST MCP 12 endpoints · 3 tools api.schedulesmcp.comSchedulesMCP
Compare sailings the way a freight desk actually books them.
REST MCP 12 endpoints · 8 tools api.loadingmcp.comLoadingMCP
Plan the stuff inside the box, to the standard, not by eye.
REST MCP 7 endpoints · 6 tools api.freightratesmcp.comFreightRatesMCP
What a lane costs this week, before you brief a forwarder.
REST 10 endpoints api.navo24.comDistance & Time
Distance and transit time by sea, inland waterway, road, rail and air, and door-to-door multimodal chains.
REST 14 endpointsREST
Plain HTTP, JSON out
Bearer-key auth, predictable envelopes and DCSA-normalised events. Copy-paste samples in curl, JavaScript and Python on every endpoint.
Browse the referenceMCP
Freight state as tool calls
Point Claude, Cursor or any MCP client at a server and let the model call tracking, schedules and load planning directly. Same key, same data.
MCP quickstartGuides
All guidesGet started
Core concepts
Guides
- Webhooks Register an HTTPS endpoint, verify the HMAC signature, and let a Navo24 product push events to you instead of polling. One model across ocean, air and the rest of the family.
- Identifiers and ports The references the APIs take: container numbers, bills of lading, AWBs, and UN/LOCODE ports.
- DCSA event feed The same tracking events in the industry-standard DCSA format, so a client that already speaks the standard plugs in without a mapping table.
- SDKs and clients Generate a typed client from the OpenAPI spec, or call the API directly with the snippets.
- Embed a tracking widget Put live tracking on a client's own site, from a zero-config hosted embed to a self-hosted proxy, without a secret ever reaching the browser.