Submit an external Vault action transaction
Record the transaction hash after the external owner executes a Vault action.
execute_safe_transaction action, submit its transactionHash.
Submitting the hash does not by itself activate the policy. Stableyard verifies the transaction receipt and the policy on chain before activation. Idempotency-Key is required.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
^0x[a-fA-F0-9]{64}$"0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
Response
Vault action
"vault_action_123"
"vault_123"
sign_policy, approve_managed_policy, install_policy, auto_supply_yield, redeem_yield, execute_payment pending, queued, processing, completed, failed, cancelled x >= 1"vault_policy_123"
Public wallet, signature, email approval, or wait instruction. Treat the action type as the discriminator and never modify transaction calldata. execute_safe_transaction is an on-chain transaction the Vault owner must execute; it includes a completion request descriptor for submitting the mined transaction hash.