List a policy's proposals
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
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/policies/497f6eca-6276-4993-bfeb-53cbbbba6f08/proposals"[ {}]Upload transaction, event or audit records to a policy POST
The owner's door into the central policy intake. Account session of the policy's POLICY_OWNER or SOURCE_CUSTODIAN; same-site JSON and an Idempotency-Key are required. The records are assessed and signed exactly as on /v1/assessments/{assessmentId}/records, and the upload is recorded on the policy's access chain. The findings stay with this policy, and its authors (the desk on a MANAGED policy) receive the findings case. Uploading changes no revision, so the uploader never becomes an author. A policy_id in the body must name this policy.
Propose a policy from signed findings or governed documents POST
Account session of a policy AUTHOR or POLICY_OWNER; same-site JSON and an Idempotency-Key are required. With findingsIds, a deterministic parameter proposer sets commerce-preflight-v2 parameters (P01, P09, P12, P13, P14, P15, P16) from the findings' distributions; every parameter cites the findings behind it and the same findings always produce the same parameters. An approved model, when named, writes only the rationale. With sourceIds, the existing document drafting runs. Alias kept on the same handler /v1/public/account/workspace/policy-platform/{policyId}/proposals.