Unarchive Fulfillment

PUT 
/api/sales-order-fulfillments/:salesOrderFulfillmentId/unarchived

Unarchive a single fulfillment, restoring it to default list results. No request body.

Required scope: orders:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Note the path segment is unarchived (the bulk endpoint uses unarchive).

The response is always HTTP 200; if the fulfillment is not 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

OK

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

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.

404

Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.

422

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.

429

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.