Re-track Shipment Tracking
POST/api/shipment-trackings/:tracking/retrack
Re-activate tracking for an expired or stopped number via 17TRACK's /retrack endpoint. 17TRACK auto-stops tracking ~30 idle days after the last event; this asks it to resume pushing updates.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Only accepted for numbers 17TRACK has stopped following — an actively-tracked number is rejected. Each number can be re-tracked ONCE (17TRACK limit -18019905).
On success the local row's stopped_at is cleared, delivery_status resets to pending (re-entering the polling set), and the row is immediately re-hydrated via /gettrackinfo.
Responses:
200 OK— re-hydrated detail payload (same shape asGET /shipment-trackings/{id})422 Unprocessable Entitywithcode: retrack_failed— 17TRACK rejected the retrack (number still active, retrack already used once, connector failure)404 Not Found— tracking ID does not exist
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
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.