Authorize a Vault policy
Authorize a pending Vault policy with the owner’s signature or the managed email code.
method: eip712_signature with the external owner’s signerAddress and signature, or method: managed_email_otp with the managed Vault’s email code. Idempotency-Key is required.
For an external-signer Vault, the signature alone does not change the Vault’s on-chain spending policy. Get an account Vault then returns an execute_safe_transaction action, and the owner, or the owner multisig, executes the returned transaction. Record it with Submit an external Vault action transaction. Stableyard verifies the transaction receipt and the policy on chain, then marks the policy active.Authorizations
HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin.
Headers
Retry key. Reuse a key only with the identical request; different input returns a conflict.
"request-key-001"
Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated.
2026-09-09 Path Parameters
Canonical account id returned by the Accounts API.
"acct_123"
Body
Response
Authorized policy
"vault_policy_123"
"vault_123"
x >= 1x >= 1draft, pending_authorization, authorized, installing, active, superseded, revoked, failed external, stableyard x >= 1Present on single-policy responses while authorization is pending.