Skip to main content
POST
GetSigningRequestDetails
Returns a signing request accessible to the API token, whatever its status and whether it originated through the API, in the MPCVault app or from a connected dApp. Reading it does not require a connected ClientSigner. The call fails with HTTP 400 (InvalidArgument, message Invalid uuid) when the request does not exist or is not accessible. The SigningRequest object uses the same payload structure as list and batch-payment responses, including wallet and management details. Queryable management requests cannot be executed with ExecuteSigningRequests. This endpoint also exposes available simulation, evmInputDataDecode, requiredApprovalCount and remainingApprovalCount. Available signedTransaction and complete signatures are visible only to full-access tokens. Read-only tokens do not receive signature bytes. pendingOperation reports the current API-user approval or eligible ClientSigner action. See Field visibility and Pending operation.
Returned payloads, simulations, decoded calldata and source metadata are reference information, not independent verification. See Verify independently.

Authorizations

x-mtoken
string
header
required

Your API token. Required for all API requests.

Body

application/json
uuid
string<uuid>
required

Unique identifier of the signing request.

Example:

"<string>"

Response

200 - application/json

OK

signingRequest
object | null

SigningRequest uses the same payload for API, MPCVault app and dApp requests across read endpoints. The selected type identifies the payload; field comments specify visibility and execution restrictions.

error
object | null

Exactly one of the two error code fields is set.