Get Shipment Tracking

GET 
/api/shipment-trackings/:tracking

Single tracking row with the FULL event timeline + integration instance descriptor. Powers the per-row timeline detail view in the Delivery Exceptions view and on entity detail pages.

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Response adds the following on top of the listing shape:

• events — ordered array of carrier events (events_payload JSON column)
• registration_error — last registration error string from 17TRACK if any
• integration_instance — the parent instance { id, name }

Responses:

• 200 OK — detail payload
• 404 Not Found — tracking ID does not exist

Request

Responses

200

OK

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.

404

Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.

429

Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.