Undo Cost Entry AI Allocation
POST/api/cost-entries/:costEntry/ai-allocation/:batch/undo
Removes the allocations one confirmation wrote and sets those proposals back to rejected. The confirmation is named by its allocation ids, not its proposal ids: a proposal can be undone, edited and confirmed again, and replaying the first Undo must not remove the later confirmation's allocations. Only allocations still tied to an accepted proposal of the batch are removed; an allocation edited, unlinked or deleted since confirming is left alone.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body:
allocation_ids(array of integers, required, 1 to 5000, distinct) — theallocation_idsthe confirm response returned.
Response: data has the same shape as the confirm result — batch_id, count (allocations removed), total, proposal_ids, allocation_ids, unallocated_after, decided_by_name, decided_at, input_hash. batch is the refreshed batch; message is a short summary.
Errors: 422 when none of the named allocations is still tied to the confirmation (already undone, or a stale replay); 422 validation errors when allocation_ids is missing; 404 when the batch does not belong to the cost entry.
Required permission: cost_entries.ai_allocate (Allocate with AI).
Authentication: Requires Bearer token (scope purchase-orders:write).
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.
Unprocessable Content
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.