DCSA Track & Trace 2.2 event feed
Standards-aligned event feed (DCSA T&T 2.2.0). Returns a bare JSON array of event objects for the containers on your account, newest first. Filter with the DCSA query parameters. IMPORTANT — two fields customers ask about:
-
emptyIndicatorCode is present ONLY on EQUIPMENT events and ONLY when the carrier reported the fill state. Per DCSA it is a required EMPTY | LADEN enum with no 'unknown' member, so rather than fabricate a value we OMIT the field when the line didn't report it (most equipment events). Do NOT rely on it as your end-of-shipment trigger — many carriers (e.g. MSC) never stamp it on the empty return. Where the carrier described the move only in words ('Empty received at CY'), we now infer EMPTY from that phrase, but coverage is still partial.
-
There is NO container-level status in this feed — it is events only. delivered / returned_empty are CONTAINER statuses, not events; read them from GET /v1/containers/{id} (the status field). To detect end-of-shipment, poll the container status: delivered = laden box handed to the consignee at the destination port; returned_empty = the empty box was returned to the depot (the true, terminal end of shipment, which happens AFTER delivered).
Request
- Base URL: https://api.trackingmcp.com
- URL: https://api.trackingmcp.com/v2/events
- Auth: HTTP bearer
Query parameters
Filter to a single container number (e.g. MSCU1234567).
DCSA event type filter.
Response
DCSA event array (the API-Version response header reports the T&T version, e.g. 2.2.0).
Changes
No recorded changes to this operation across all 1 revision of this API.