Skip to main content
POST
GetSigningRequestList
Returns the signing requests of a vault: pending, succeeded and failed, whether they were created through the API, in the MPCVault app or by a connected dApp. There is no status filter. Results are newest first by default. Paginate with page (starting at 1) and limit (1 to 100, default 10). Set sortOrder to SORT_ORDER_ASC for oldest first. The call fails with HTTP 400 (InvalidArgument, message Invalid uuid) when the vault does not exist or the API token cannot access it. Each element of signingRequests is a SigningRequest object: the common fields and at most one payload field, with their encodings. Data types and encodings lists the conventions that apply to all fields.
Every request in the response carries its full payload and simulation. A page of very large requests, for example 100 requests with about 128 KiB of calldata each (about 13 MB), exceeds the 10 MiB limit on the protobuf message that the REST gateway accepts from the gRPC server, and most gRPC clients accept 4 MiB by default. The call then fails with RESOURCE_EXHAUSTED (HTTP 429): request a smaller limit. A single request with very large calldata or simulation can exceed these limits on its own.

Authorizations

x-mtoken
string
header
required

Your API token. Required for all API requests.

Body

application/json
vaultUuid
string<uuid>
required

UUID of the vault whose signing requests are listed. The API token must have access to it.

Example:

"9f5ee5fb-07f5-470c-a2ff-081e2d6d107a"

page
default:1

Page number, starting at 1.

Required range: x >= 1
Example:

1

limit
default:10

Number of signing requests per page.

Required range: 1 <= x <= 100
Example:

10

sortOrder
enum<string>
default:SORT_ORDER_DESC

Order by creation time: SORT_ORDER_DESC is newest first, SORT_ORDER_ASC is oldest first.

Available options:
SORT_ORDER_DESC,
SORT_ORDER_ASC

Response

200 - application/json

Success

signingRequests
(object | null)[]
error
object | null

Exactly one of the two error code fields is set.