Update Repair Shipment Status
POST/api/repairs/:repair/shipments/:shipment/status
Sets a shipment's status by hand (normally it is updated from carrier tracking). A voided shipment, or one already at that status, is returned unchanged.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Effects:
- outbound in transit — units are marked outbound and the customer is emailed that the repair is complete and shipped;
- outbound delivered — units are marked delivered and the repair rolls up to returned;
- inbound in transit — units appear on the warehouse's expected inbound list;
- inbound delivered — logged as arrived, awaiting the receive scan.
Fields:
status(string, required) —in_transit,deliveredorexception.at(date-time, optional) — when it happened; defaults to now. Setsshipped_at/delivered_at.
Authentication: Bearer token with the repairs:write scope.
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.