Guides

Build on the freight spine.

Start with the first call, then wire authentication, MCP clients, webhooks and error handling. Every guide is short and to the point.

Get started

Getting startedContainer tracking API quickstart: your first Navo24 call in two minutes with no key, then an API key and a tracked shipment.AuthenticationBearer keys, the per-product prefixes, and the one family credential.

Core concepts

MCP quickstartPoint Claude, Cursor or any MCP client at a Navo24 server and let the model call freight tools.Connect Navo24 to any AI assistantAdd 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 limitsResponse envelopes, error codes, and the usage headers that ride on every call.

Guides

WebhooksRegister 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 portsThe references the APIs take: container numbers, bills of lading, AWBs, and UN/LOCODE ports.DCSA event feedThe 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 clientsGenerate a typed client from the OpenAPI spec, or call the API directly with the snippets.Embed the Navo apps on a client siteTracking, 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 quickstartPut a Navo map on a page, add place search and reverse geocoding, and show ports, airports and rail terminals. MapLibre, Leaflet and plain HTTP.