Track any shipment.
One endpoint.

It is a REST API that returns real-time container, bill of lading (BL) and vessel tracking data as clean JSON. You pass a container or BL number to a single endpoint and get the current status, full port/event timeline, route, ETA and vessel information — across 170+ ocean carriers, without scraping carrier websites.

Create a free account, open the Developer section of your dashboard and generate a key. Requests authenticate with a Bearer token in the Authorization header — no SDK or approval process required.

Yes. The free tier includes API access so you can integrate and test end-to-end at no cost, and there are no per-call charges. The limit is your plan's monthly shipment allowance — how many new references you add in a billing cycle, not how many you may track at once. Shipments added in earlier cycles keep tracking for free until they are delivered, so you can have considerably more in transit at any moment than your monthly number. See pricing for higher tiers.

The API covers 170+ ocean carriers including Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, Evergreen, COSCO, ZIM and many regional lines — one endpoint and response shape for all of them.

Yes. There are dedicated endpoints for container numbers and for bill of lading (BL) numbers, and both return the same JSON structure, so your integration code stays identical.

Data is pulled continuously from carrier and port sources, and the API responds in under ~400ms on average with 99.9% uptime, so it is suitable for real-time dashboards, TMS/ERP integrations and customer notifications.

120 requests per minute per API key by default, over a fixed 60-second window. Every response carries X-RateLimit-* headers, not just the ones that fail, so you can pace against the remaining count instead of waiting to be refused. Over the limit you get a 429 with Retry-After in seconds. Higher limits can be configured per plan.

Not necessarily — 402 has two distinct causes and data.error tells you which. "shipment_limit_reached" means you have used every shipment slot for the billing period; "payment_overdue" means a payment failed and the grace period has ended. Branch on data.error rather than the message text. Either way, references you already track keep updating; what is blocked is adding new ones.

Yes — the Developer page shows used, limit and remaining live, and the same figures are available to your integration. Poll that rather than learning your position from a 402.

No — keys are stored hashed, so we genuinely cannot read an existing one back. Issue a new key and revoke the old one. That is a deliberate design choice: a key we could show you is a key anyone who reached our database could show themselves.

Two integrations exist today and you can use them now. Webhooks push shipment events to any endpoint you own — set them up under Dashboard, Developer, Webhooks. The REST API gives you container, bill of lading and vessel tracking in your own tools, documented at /developer, and there is a SeaRates-compatible version of it at /developer/searates if you already use theirs. Both need developer mode switched on for your account. Zapier and Make, Google Sheets, Slack alerts, Microsoft Teams and an MCP server for Claude, ChatGPT and Cursor are not built. You can ask for them: open Settings, then Integrations, and press the button beside the one you want. That records your request and shows you how many other accounts have asked for the same thing, which is what decides the order we build them in. Nothing there is scheduled and we do not promise a date — if someone tells you one of these is coming soon, that is not something we have said. Anything not on that list can be requested from Dashboard, Feature requests, where you can also vote on what other customers have asked for.