Refresh Shipment Tracking
POST/api/shipment-trackings/:tracking/refresh
On-demand refresh — hits 17TRACK's /gettrackinfo synchronously and re-hydrates the local row (events, status, sub_status, estimated_delivery_at, etc.). Returns the same shape as GET /shipment-trackings/{id} so the timeline detail view can swap the payload in-place.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Responses:
200 OK— refreshed detail payload (same shape as GET)422 Unprocessable Entitywithcode: refresh_failed— 17TRACK API rejected the request (quota exceeded, rate-limited, connector failure). The timeline detail view surfaces this as a friendly error toast.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.