The short answer
A container tracking API sends milestones for a container number straight into your own system. For most importers the right choice is a tool that combines webhooks, one event model across modes and a flat monthly price, because the cost of an API is rarely the call, it is the engineering time to maintain it.
If you track fewer than a few hundred containers a month and also move LTL and parcel, a flat plan with an included API is the simplest buy. If you track thousands of containers and nothing else, a per-container specialist can cost less. This page shows how to tell which you are. For a no-code view, see container tracking software, and for the API itself, the shipment tracking API page.
Four ways to get container data into your system
Shipping line APIs and portals. Accurate for that line, and one integration per line. Fine if 90 percent of your boxes sail with one carrier. Painful with six.
Ocean-only tracking APIs. Built for containers, usually priced per container or by quote, with deep milestone coverage. Strong for forwarders and importers who handle only ocean freight. Our Terminal49 alternatives and Shipsgo alternatives posts compare two of them in detail.
Enterprise visibility APIs. Network integrations across modes with quote-based contracts. Powerful, and sized for large shippers. Read project44 alternatives before a sales call.
Multi-mode APIs with flat plans. One call accepts container, bill of lading, air waybill, PRO and parcel numbers and returns the same event shape. This is the lane ShipmentVisibility targets, with the API in Pro from $499 a month. The trade-off is an ocean allowance, 120 containers a month on Pro and 400 on Enterprise.
Polling versus webhooks, with numbers
Assumed example, so you can swap in your own figures. An importer tracks 150 containers a month. Each container is followed for about 18 days from sailing to empty return. If a developer polls every four hours, that is 6 calls a day.
| Method | Calls per container | Calls per month | New information |
|---|---|---|---|
| Polling every 4 hours | 6 a day x 18 days = 108 | 16,200 | Roughly 8 changes per container |
| Polling every 24 hours | 18 | 2,700 | Same 8 changes, found up to a day late |
| Webhooks | About 8 events | 1,200 | Every change, when it happens |
Polling every four hours makes 13 times more calls than webhooks and still lags the real event by up to four hours. Daily polling is cheaper but a gate-out or a free-time change can sit unnoticed for 24 hours, which on a container with two free days left is the whole margin. That is why demurrage and detention charges are the usual reason importers move from polling to webhooks.
Ask any vendor three questions: does a webhook fire on an ETA change, how are failed deliveries retried, and can you replay missed events. The ShipmentVisibility webhooks cover shipment.updated, shipment.exception, shipment.delivered and eta.changed.
What to test in a 14 day trial
Send 20 real containers, not demo numbers. Include two from your slowest shipping line, one transshipped box and one bill of lading you only have as a master. Then score the API on the table below, using the vendor documentation and your own logs.
| Test | What good looks like | Red flag |
|---|---|---|
| Number input | Container, booking and bill of lading accepted, carrier detected | You must pick the line yourself for every call |
| Event model | Same milestone codes for every line, with time zone and location | Free text status copied from each line |
| ETA changes | New ETA arrives by webhook with a confidence range | ETA only visible on a manual refresh |
| Webhook delivery | Signed requests, retries on failure, replay of missed events | Fire and forget, no replay |
| Billing | Price per month or container is on the page and matches the invoice | Usage overage only shown after signup |
| Other modes | Parcel, LTL and air on the same call if you need them | Ocean only when you also ship LTL |
Industry bodies are standardizing this data. The Digital Container Shipping Association publishes an open track and trace standard that major lines are adopting, which is one more reason to prefer a vendor with a clean milestone model over one that passes text through.
Container tracking API options compared
| Option | Best for | Pricing model | Where it wins | Watch out for |
|---|---|---|---|---|
| Shipping line APIs | Importers loyal to one line | Usually free with an account | Most accurate for that line | One integration per line |
| Ocean-only API vendors | Forwarders with thousands of containers | Per container or by quote, confirm on the vendor page | Deep ocean coverage | No LTL, parcel or air |
| Enterprise visibility platforms | Large multi-mode shippers | Annual contract by quote | Network data across modes | Sales cycle, high minimums |
| ShipmentVisibility Pro | Importers and shippers who also ship LTL and parcel | $499 a month, 4,000 shipments, 120 containers | One event model, public price, no contract | Ocean allowance caps at 400 containers on Enterprise |
Prices marked confirm are vendor-specific figures we could not verify publicly, so we do not guess them. Check each vendor page on the day you buy. Teams that also automate paperwork around imports sometimes add an OFAC sanctions screening tool beside tracking before an overseas order ships.
The next step is cheap. Run your 20 test containers through the number check on this page, then pick Pro to get an API key and compare the response with the table above. For a wider tool shortlist, read best container tracking software and ocean freight tracking software compared.
FAQ
What is a container tracking API?
A container tracking API lets your software send a container number or bill of lading and receive milestones such as vessel departure, arrival, discharge, gate out and empty return. Your systems read the same data a person would find on the shipping line site, without anyone opening it.
How much does a container tracking API cost?
Pricing models vary. Some vendors charge per container, some per API call and some sell enterprise contracts by quote. ShipmentVisibility includes the API in Pro at $499 a month with 120 ocean containers and 4,000 shipments, and Enterprise at $1,499 with 400 containers.
Should I use webhooks or polling for container tracking?
Use webhooks. A container changes status a handful of times in 30 days, so polling every few hours asks the same question thousands of times for no new answer. Webhooks send one message when a milestone changes and cut calls by more than 90 percent.
Can one API track containers and parcels?
Yes, if the vendor returns one event model for every mode. ShipmentVisibility accepts container, bill of lading, air waybill, PRO and parcel numbers on the same call, so a developer writes one integration.