Change Shipment Tracking Carrier
POST/api/shipment-trackings/:tracking/change-carrier
Correct a mis-detected carrier via 17TRACK's /changecarrier endpoint and re-hydrate the row under the new carrier. 17TRACK auto-detects the carrier from the number format when registering and sometimes picks wrong — this fixes it without stopping/re-registering.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
17TRACK caps carrier changes at 5 per number (error -18019807).
Request body:
carrier_code(integer, required) — 17TRACK numeric carrier key the shipment actually ships with. Carriers configured in SKU.io (Settings → Shipping Carriers) can carry aseventeen_track_carrier_code; the full directory is at https://res.17track.net/asset/carrier/info/apicarrier.all.json.
On success the local row's carrier_code is updated, carrier_name clears (re-hydrated on the next /gettrackinfo), and the tracking history reloads under the new carrier.
Responses:
200 OK— re-hydrated detail payload422 Unprocessable Entitywithcode: change_carrier_failed— 17TRACK rejected the change, or validation failed (missing/invalidcarrier_code)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.