Execute Signing Requests

Endpoint

rpc ExecuteSigningRequests(ExecuteSigningRequestsRequest) returns (ExecuteSigningRequestsResponse)

Messages are in mpcvault.platform.v1. Full access is required. The configured eligible API ClientSigner must be connected and have the required key access. The request can originate through the API, MPCVault app or a dApp. Queryable vault and organization management requests cannot be executed with this method. Read Get Signing Request Details before execution; pending_operation is a hint, and execution revalidates permissions and policy. Use Approve Signing Request when this API user’s approval is still needed.

Request

Field	Type	Required	Description
`uuid`	string	Yes	One supported wallet signing request UUID.

Response

Field	Type	Description
`error`	Error	Error information when returned.
`tx_hash`	string	Available signed transaction hash; does not confirm broadcast or on-chain execution. Messages can have no hash.
`signatures`	SignatureContainer	Available complete signature results in signing order, not MPC shares.
`signed_transaction`	string	Available signed transaction using the network-specific encoding. Absent for messages. Co-signed transactions can still need other signatures.

See Introduction for broadcast rules. Message and raw signing do not broadcast transactions.

Getting Started

Wallets

Signing Requests

Batch Payments

Deposit & Sweep

TRON Watch Address

Execute Signing Requests

Endpoint

Request

Response