Skip to main content
POST
ExecuteSigningRequests
Requires full access. Signs one supported wallet signing request identified by uuid, whether the request was created through the API, the MPCVault app or a connected dApp. The eligible API ClientSigner must be configured, connected and hold the required key access. For API-created requests, callbackClientSignerPublicKey selects the callback signer when the request is created. Read GetSigningRequestDetails before execution. Its pendingOperation can identify an eligible ClientSigner target, but execution revalidates permissions and policy. If the API user’s approval is still needed, use ApproveSigningRequest. Queryable vault and organization management requests cannot be executed with this method. Existing wallet requests include supported dApp transactions/messages, batch payments and other wallet payloads beyond the types accepted by CreateSigningRequest. The response returns available txHash, complete signatures and signedTransaction. A co-signed transaction can still need other parties’ signatures. Signing success does not confirm successful broadcasting or on-chain execution. For built-in networks, MPCVault broadcasts supported transactions by default. Introduction describes broadcast rules and result handling, including custom EVM networks. Messages and raw signing do not broadcast a transaction.

Authorizations

x-mtoken
string
header
required

Your API token. Required for all API requests.

Body

application/json

ExecuteSigningRequestsRequest requires a full access token with access to the request and a configured, online API ClientSigner. Only supported wallet requests can be executed; queryable management requests cannot.

uuid
string<uuid>
required

UUID of one supported wallet signing request to execute, whether created through the API, MPCVault app or a connected dApp. A pending request requires the configured ClientSigner and its current vault key access. Management requests can be queried but cannot be executed through this method. Execution revalidates permissions and policy.

Example:

"<string>"

Response

200 - application/json

OK

error
object | null

Exactly one of the two error code fields is set.

txHash
string

Signed transaction hash, when available. It does not confirm successful broadcasting or on-chain execution. Message requests may have no transaction hash.

Example:

"<string>"

signatures
object | null

Signatures contains complete signature results in signing order, when available. See SignatureContainer; these are not MPC signature shares.

signedTransaction
string

Serialized signed transaction, when available, using the encoding on SigningRequest.signed_transaction. Absent for messages; co-signed transactions may still need other parties' signatures.