Developer portal
Freight API for developers. Shipment data your code can call directly.
Send a container, an air waybill or a lane; get back status, route, milestones, schedules, rates and load plans. Every freight API here 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 freight 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 MCP 12 endpoints · 8 tools api.navo24.comDistanceMCP
How far and how long, door to door, by sea, river, road, rail or air.
REST 14 endpoints api.navo24.comMapsPlatformMCP
Find any city, port, airport or rail terminal, and put it on the map.
REST 10 endpoints api.navo24.comCarbonMCP
CO2e of any shipment, by sea, air, road or rail, per ISO 14083 and the GLEC Framework.
REST 3 endpoints parcel.navo24.comParcelMCP
Track a parcel by its number: carrier detected from the number, every connected postal and courier source asked at once.
REST 2 endpoints vessel.navo24.comVesselMCP
Where a vessel is now, from live AIS, with its particulars and port calls.
REST 2 endpoints road.navo24.comRoadMCP
Truck route, distance, driving time and an ETA that counts driver rest, with progress from a shared live position.
REST 2 endpoints rail.navo24.comRailMCP
Rail route through terminals, transit time, and the status of a container with its rail moves.
REST 2 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
- MCP quickstart Point Claude, Cursor or any MCP client at a Navo24 server and let the model call freight tools.
- Connect Navo24 to any AI assistant Add the Navo24 container-tracking MCP server to Kimi, Qwen, DeepSeek or any other MCP client, with an API key or your TrackingMCP sign-in.
- Errors and rate limits Response envelopes, error codes, and the usage headers that ride on every call.
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 the Navo apps on a client site Tracking, freight rates, sailing schedules and the AI assistant on a client's own website, in the client's brand, with one script tag and a domain-locked key.
- MapsPlatformMCP quickstart Put a Navo map on a page, add place search and reverse geocoding, and show ports, airports and rail terminals. MapLibre, Leaflet and plain HTTP.