Skip to main content
POST
Resimulation
Re-runs the simulation of a pending signing request and returns the stored simulation. The encoding of simulation is described under Simulation: base64 in JSON, decoding to UTF-8 JSON text in a network-specific form, for reference only. A successful re-run replaces the stored simulation with the result of the run. If the simulation provider returns an error, or the organization’s simulation allowance is used up, the call still succeeds and simulation is empty. A simulation that does not finish within 5 seconds fails a custom transaction with an error, and returns the earlier stored simulation for a dApp transaction. A returned simulation therefore does not show that it was just re-run. The request must be pending, belong to a vault the API token can access, and have been created by the same API user. Only custom transactions and EVM dApp transactions are simulated; for any other request simulation is empty.

Authorizations

x-mtoken
string
header
required

Your API token. Required for all API requests.

Body

application/json
signingRequestUuid
string<uuid>
required

UUID of the signing request to be simulated. It must be pending and must have been created by the same API token.

Example:

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

Response

200 - application/json

Success

simulation
string<byte>
required

Simulation of the signing request.

error
object | null

Exactly one of the two error code fields is set.