Dismiss Pending Changes
POST/api/purchase-orders/:purchase_order/changes-since-sent/dismiss
Dismiss the pending post-send changes on a purchase order without re-sending it. Use this when an order was edited after it was sent but the change does not need to go to the supplier — the supplier keeps the last sent revision.
Clears the pending-changes marker (the order returns to submitted) and remembers the dismissed state, so routine saves that leave the order unchanged will not raise it again. Any further material change to the order (lines, quantities, pricing, terms) re-raises the pending-changes state.
No new revision is created — revision_number is unchanged and the last sent revision remains what the supplier has. Dismissing an order with nothing pending is a no-op.
Path params:
purchase_order(required): id of the purchase order.
Returns the updated purchase order under data.
Authentication: Requires Bearer token.
Requires permission: purchase_orders.update
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.