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 off-chain EIP-712 signature alone does not modify the Safe. Authorization is followed by an execute_safe_transaction action, returned by Get an account Vault, which the Safe owner or owner multisig must execute before Stableyard can verify the Zodiac module and mark the policy active. Record that transaction with Submit an external Vault action transaction.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
Use this for retry-safe payment operations from your backend.
"payment-request-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.