Reject Cost Entry AI Allocation Batch
POST/api/cost-entries/:costEntry/ai-allocation/:batch/reject
Discards everything the batch still offers: its pending, ready, held and stale proposals become rejected. Proposals already confirmed are untouched (use Undo Cost Entry AI Allocation to remove those). Nothing is allocated.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
No request body.
Response: data.rejected (number of proposals rejected), batch (the refreshed batch) and message.
Errors: 422 when the batch is still being proposed; 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.