Archive Fulfillment
PUT/api/sales-order-fulfillments/:salesOrderFulfillmentId/archive
Archive a single fulfillment. No request body. Archived fulfillments are hidden from default list results but remain retrievable.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The response is always HTTP 200; if the fulfillment is already archived, the JSON status is warning with a per-field entry under warnings.
Returns 404 for an unknown ID. Requires the orders:write token 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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.