Server — read the approval requirements in force
Readable by any member: names which of the account’s actions need consent
before attempting one. Also needed to use PUT, which replaces the
section wholesale — changing one action means merging against this value
first.
Empty object when nothing is governed; that is an answer, not a 404.
Authorizations
Headers
Request proof: a compact ES256 JWS, signed with the server's registered key, binding this request to a single-use nonce from GET /nonces. The JWS header is RequestSigningProofHeader and its payload is RequestSigningProofPayload. Required when the request carries a DYN API token and no JWT, and a server signer with a registered key controls the resource. A proof that is present is always verified.
4096^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$Path Parameters
Response
The governance section in force