What is a container tracking API and how does it work?
A container tracking API lets software request the live status of any shipping container through a single, predictable interface — instead of scraping dozens of carrier websites. This guide covers how these APIs work, how data stays fresh, and what to look for when choosing one.
What a container tracking API is
An API — application programming interface — is a contract that lets one piece of software ask another for data in a structured way. A container tracking API exposes shipment visibility as that kind of programmable service: send a container number, get back its status.
Behind the endpoint sits the hard work described in our fundamentals guide — connecting to carriers, terminals, and AIS feeds, then reconciling everything into one clean timeline. The API hides that complexity behind a single request.
The core idea
You integrate once, against one schema. The provider absorbs the mess of per-carrier formats, logins, and quirks on your behalf.
How a request works
Most modern tracking APIs are REST APIs that speak JSON over HTTPS. You authenticate with a secret key, then make a simple GET request for a container. A typical call looks like this:
curl https://api.cargodocked.com/v1/containers/MSCU7432105 \ -H "Authorization: Bearer sk_live_..."
The response comes back as structured JSON — status, ports of loading and discharge, vessel, ETA, and the latest event — ready to drop straight into your application. With Cargo Docked, each successful lookup costs a single credit.
One normalized schema across carriers
The single biggest reason to use an API rather than carrier portals is normalization. Every carrier models its data differently: different event names, date formats, port codes, and status vocabularies. Parsing each one is brittle and never-ending.
A good tracking API returns the same response shape no matter which carrier is involved. Your code handles one schema; the provider maps 180+ carriers into it behind the scenes.
Polling and data freshness
Polling means re-requesting a container on a schedule to check whether anything has changed. It is the simplest model: make a GET request, inspect the response, act on new events. Because each call costs one credit, you control exactly when and how often you check.
Good to know
Cargo Docked data refreshes multiple times per day per container, so a well-timed polling schedule captures events within minutes of when they happen at the port or terminal.
How to choose a container tracking API
Not all tracking APIs are equal. When evaluating one, weigh these factors:
Cargo Docked is built around exactly these priorities: one normalized schema, 180+ carriers, predictive ETAs, and 10 free credits to start.
Frequently asked questions
Do I need to know the carrier before calling the API?
No. You can pass just the container or bill-of-lading number and the API identifies the carrier and resolves the correct data for you.
What does one lookup cost?
With Cargo Docked, one credit equals one container lookup that returns full status, route, vessel, and the latest events.
Can I track many containers at once?
Yes. A bulk endpoint lets you track up to 1,000 containers in a single request — ideal for forwarders and control-tower dashboards.
Up next
What is an API key?