Reopen Fulfillment Order Discrepancy
POST/api/fulfillment-orders/:fulfillmentOrder/reopen-discrepancy
Reverse a prior discrepancy acceptance and re-open the discrepancy alert for a fulfillment order. This clears the accepted stamp (discrepancy_accepted_at / discrepancy_accepted_by) and re-fires the discrepancy alert so the mismatch is surfaced again.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
This does NOT reverse an already-recorded shipment — the lines that shipped genuinely shipped; it only re-opens the discrepancy state so it can be reviewed or accepted again.
Returns the fulfillment order with the acceptance cleared.
Authentication: Requires Bearer token.
Required permission: fulfillment_orders.ship (Fulfillment Orders → Ship) 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
- 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.
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.