SDKs & tools
Everything you need to build on Navo24.
OpenAPI specs for every product, a typed client in your language in one command, ready Postman collections, MCP servers for AI assistants and a test button for your webhook receiver.
Pick how your system talks to Navo24.
REST API
Call the API from your own code
Your backend sends a container, an air waybill or a lane to https://api.navo24.com/v1/<product> with a bearer key and gets JSON back. Use a generated client, the Postman collection or plain HTTP.
Read the quickstartMCP
Let an AI assistant call the tools
Claude, Cursor, ChatGPT or any MCP client connects to a Navo24 MCP server and calls tracking, schedules, rates and load planning as tools. No client code to write.
MCP quickstartClient libraries
A typed client in your language, in one command.
Each product publishes an OpenAPI 3 spec that already points at api.navo24.com. Run OpenAPI Generator against it and you get models, an API class per section and auth handling. We generate all six targets below from our own specs before every release.
Official Navo24 packages for npm, PyPI and the other registries are not published yet. Until they are, generate the client yourself: it stays in step with the API every time you regenerate.
A walkthrough with a hand-written fetch wrappernpx @openapitools/openapi-generator-cli generate \
-i https://navo24.com/developers/openapi/tracking.json \
-g typescript-fetch \
-o ./navo24-tracking-tsnpx @openapitools/openapi-generator-cli generate \
-i https://navo24.com/developers/openapi/tracking.json \
-g python \
-o ./navo24-tracking-pynpx @openapitools/openapi-generator-cli generate \
-i https://navo24.com/developers/openapi/tracking.json \
-g php \
-o ./navo24-tracking-phpnpx @openapitools/openapi-generator-cli generate \
-i https://navo24.com/developers/openapi/tracking.json \
-g java \
-o ./navo24-tracking-javanpx @openapitools/openapi-generator-cli generate \
-i https://navo24.com/developers/openapi/tracking.json \
-g csharp \
-o ./navo24-tracking-dotnetnpx @openapitools/openapi-generator-cli generate \
-i https://navo24.com/developers/openapi/tracking.json \
-g go \
-o ./navo24-tracking-goSwap tracking.json for air.json, schedules.json, loading.json or rates.json to get the other products. Needs Node.js 18+ and Java 11+; the openapitools/openapi-generator-cli Docker image takes the same flags.
OpenAPI and Postman
Specs and collections for every product.
Download the spec for code generation or contract tests, or import the collection and send your first request in a minute. Set the apiKey variable to your key; baseUrl is already filled in.
Bruno and Insomnia import the same collection or the OpenAPI file directly.
Tools
More tools that ship with every key.
Code samples
Every endpoint in the reference has copy-paste requests in curl, JavaScript and Python, with real responses.
Browse the referenceMCP servers
One MCP server per product, plus mcp.navo24.com for distance, CO2e, vessels and flights. Same key as the API.
Navo24 MCP serverWebhook test delivery
Send a signed test event to your receiver from any product and check headers, envelope and retries end to end.
Webhooks guideEmbeddable apps
Tracking, rates and schedules on a client site in its own brand, with one script tag and a domain-locked key.
Embed the appsDCSA event feed
Track & Trace events in the DCSA shape, for systems that already speak the standard.
DCSA feedErrors and rate limits
One error envelope across products, the status codes to branch on and how retries should back off.
Errors and limitsWebhooks
Test your receiver
Create a webhook, then ask us for a ping. It travels the same path as a real event: same headers, same signature, same retry ladder.
POST /webhooks/{id}/testcurl -X POST https://api.navo24.com/v1/tracking/webhooks/{id}/test \
-H "Authorization: Bearer $NAVO24_API_KEY"