Remove Fulfillment Order from Merge Group
POST/api/fulfillment-orders/:fulfillmentOrder/unmerge
Remove this fulfillment order from its merged shipment group (pre-dispatch only). If the removal leaves fewer than two members, the whole group dissolves automatically.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Returns the fulfillment order with refreshed lines and warehouse. 409 when the group has already been dispatched; 422 when the fulfillment order is not in a merge group.
Authentication: Requires Bearer token.
Required permission: fulfillment_orders.update (Fulfillment Orders → Edit) and fulfillment_orders.index (Fulfillment Orders → View). A token also needs its orders scope; the owner needs these role permissions.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Conflict
Response Headers
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.