Apply Fulfillment Order Line Update
POST/api/fulfillment-orders/:fulfillmentOrder/apply-line-update
Apply a quantity change to a submitted fulfillment order in place. When a quantity increase created a separate fulfillment order for the extra units, this absorbs that fulfillment order back into this one and pushes the enlarged line set to the shipping provider as an update.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The provider update is attempted first: if the provider rejects it (for example, the order can no longer be edited), the change is rolled back and the response reports provider_ineligible so you can keep the separate fulfillment order instead.
Always returns 200 with an outcome of success (grown and confirmed by the provider), provider_ineligible (provider rejected the update; rolled back), or not_update_capable (no registered provider order, a shipment already exists, or the provider has no in-place update). data is the refreshed fulfillment order and message is a human-readable summary.
Authentication: Requires Bearer token.
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.