SDK — replace the approval requirements for a business account
Replaces the governance section wholesale, matching the enclave: a caller sending one action’s rules drops the others. Requires step-up authentication, because governance decides what every other mutation requires.
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"
Body
SDK setGovernance body. Replaces the whole section, so an absent governance field is refused rather than read as a request to delete every requirement — send an empty object to clear.
Approval requirements keyed by governed action. Replaced wholesale, so a caller changing one action must send the others back unchanged.
Whether the change applies the moment its quorum is met, or waits for an explicit execute. Read only on the first call, where it is stamped into the intent you sign; after that the signed intent is the authority. Defaults to true, because a change holding all its consent while waiting for a button press tends to be forgotten, and the deadline covers execution too.
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.
Response
Governance replaced; the new document version returned
The new version of the signed authorization document.