Accept, split or reject a proposal
Account session of a policy AUTHOR or POLICY_OWNER; same-site JSON and an Idempotency-Key are required. ACCEPT saves the candidate as a new DRAFT revision; for a findings proposal SPLIT accepts only the named checks (ruleIds such as ["P14"]) and returns the others to their previous values. The existing review, assurance and shadow gates carry the revision to APPROVED_FOR_SHADOW; nothing here reaches production. Alias kept on the same handler /v1/public/account/workspace/policy-platform/{policyId}/proposals/{proposalId}/decisions.
Authorization
AccountSessionCookie The signed HttpOnly account session the web app holds after sign-in (also accepted as a Bearer acct_ token).
In: cookie
Path Parameters
uuiduuidHeader Parameters
Request Body
application/json
0 < valueValue in
- "ACCEPT"
- "REJECT"
- "SPLIT"
1 <= length <= 4000items <= 120[]Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/policies/497f6eca-6276-4993-bfeb-53cbbbba6f08/proposals/497f6eca-6276-4993-bfeb-53cbbbba6f08/decisions" \ -H "Content-Type: application/json" \ -d '{ "expectedSequence": 1, "action": "ACCEPT", "reason": "string" }'{}Read a proposal, its candidate revision, findings and cited evidence GET
Previous Page
Replay current against proposed on the assessed records POST
Account session with READ access; same-site JSON and an Idempotency-Key are required. Both configurations are evaluated by the production commerce-preflight evaluator on identical records at their transaction time, scoped to the checks the proposal changes. Money is totalled by finding category in each transaction currency without conversion, false holds (held records with no exposure finding) are counted, and caps and coverage are explicit. Nothing is stored, sent or executed.

