Skip to main content

Documentation Index

Fetch the complete documentation index at: https://sage-f6b5014e.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
POST /execute

The server — which holds Execute permission on the multisig — builds, signs, and broadcasts vaultTransactionExecute autonomously. No client wallet signature is required, because /sponsor/create adds the server keypair as a member with Permission.Execute. After a successful execution, the server updates patterns, appends to the event log, and fires /sponsor/close to reclaim rent. There are three ways to identify the transaction to execute:
  1. Raw on-chain params — multisigPda + transactionIndex (used by the client right after proposing)
  2. By proposal — proposalId
  3. Latest in-review — vaultAddress (resolves the most recent in-review proposal)

​
Request

{ "proposalId": "uuid-of-proposal" }
or 
{ "vaultAddress": "…" }
or 
{ "multisigPda": "…", "transactionIndex": "7" }
FieldTypeDescription
proposalIdstringStored proposal ID
vaultAddressstringVault address — resolves the latest in-review proposal
multisigPdastringMultisig config account (with transactionIndex)
transactionIndexstringOn-chain transaction index (with multisigPda)

​
Response

{
  "status": "executed",
  "proposalId": "uuid-of-proposal",
  "signature": "…"
}
statusMeaning
executedCo-signed and confirmed; signature present
already_executedWas already executed; returns the prior signature
already_rejectedProposal was rejected; nothing to do
On failure the body includes an error string.