Track container location and status by bill of lading or container number using a major ocean carrier's tracking API
domain: developer.maersk.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for the Maersk Developer Portal and subscribe to the Track and Trace API product to receive a consumer key
Send a GET request to the tracking endpoint with either the bill of lading number or container number as the query parameter
Parse the response's transportEvents array to extract event type, location, actual/estimated time, vessel name, voyage number, and facility code for each milestone
Identify key milestone events such as GATE_IN, VESSEL_DEPARTED, VESSEL_ARRIVED, GATE_OUT, and EMPTY_RETURNED to build a milestone timeline
Display or store the tracking data noting the source field on each event to distinguish carrier-confirmed actual events from estimated future events
Known gotchas
The Maersk Track and Trace API returns events for Maersk-operated voyages; for multi-carrier shipments, separate API calls to each carrier's tracking API are required
Estimated times of arrival are recalculated continuously and may change significantly; downstream systems that cache ETA must refresh at regular intervals
Container tracking visibility begins at gate-in at the origin port; tracking data for inland pre-carriage before terminal gate-in is typically not available from the carrier API
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?