SDK — list the governed mutations awaiting approval
Every proposal for the account, newest first. Any member may read them: knowing what is pending is what lets an approver act, and the list carries no signing material — only who has already consented.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
ID of the environment
36^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"95b11417-f18f-457f-8804-68e361f9164f"
ID of the business account
36^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"95b11417-f18f-457f-8804-68e361f9164f"
Query Parameters
Return only proposals in this state
Lifecycle of a governed mutation awaiting approvals. Only pending accepts approvals; the other three are terminal.
pending, executed, vetoed, expired Response
The account's proposals
A business-account mutation that an approval requirement can gate.
addMember, removeMember, updateMemberRole, transferOwnership, createWallet, linkWallet, removeWallet, addSignerToWallet, removeSignerFromWallet, setGovernance, defineRole, deleteRole Lifecycle of a governed mutation awaiting approvals. Only pending accepts approvals; the other three are terminal.
pending, executed, vetoed, expired Who proposed it. They can never approve their own intent, so they are never counted toward a requirement.
The initiator's proposal, signed with their session key. Built by the API, not the client — sign these exact bytes verbatim, because re-serializing can change them and invalidate the signature.
autoExecute is inside the signed bytes, so an approver consents to it and nothing can flip it afterwards.
The one deadline for the whole proposal, derived from the signed intent's createdAt. Past it the proposal accepts no further approvals AND can no longer be executed.
When it left pending; null while still open.
Whether this applies as soon as its quorum is met, or waits for an explicit execute. A copy of the flag inside the signed intent, which is the authority. An approver needs this to know whether their approval is the one that lands the change.
The users this change is about, resolved for display — the member being added, the signer being removed, the new owner. Empty for a change that names no user, such as setGovernance.
Every governance rule matching this proposal, with how close each is. Do NOT derive progress from approvals — that counts rows, including approvers outside a rule's pool and approvers demoted since they signed.
Absent means the tally is unknown (not fetched, or no longer pending); an empty array means nothing is outstanding. Treat the two differently.