Cessio Docs
ReferenceTxExecute

Submit the signature for a pending action

Two forms. Singular: `{actionId, signature}`. Batch: `{signatures: [{actionId, signature}, …]}` (max 50) — sign everything a call handed you in ONE request. Action ids come from the call that needed them (quote, accept, deposit accept, withdrawal) or from `GET /tx/pending`. `signature` is the base64 Ed25519 signature over the RAW bytes of that action's `hash`. Successful execution advances whatever flow the action belongs to (e.g. a quote whose allocations are all signed becomes visible to the taker); the action then disappears from `/tx/pending`.

POST
/tx/execute

Two forms. Singular: {actionId, signature}. Batch: {signatures: [{actionId, signature}, …]} (max 50) — sign everything a call handed you in ONE request. Action ids come from the call that needed them (quote, accept, deposit accept, withdrawal) or from GET /tx/pending. signature is the base64 Ed25519 signature over the RAW bytes of that action's hash. Successful execution advances whatever flow the action belongs to (e.g. a quote whose allocations are all signed becomes visible to the taker); the action then disappears from /tx/pending.

Authorization

ApiKeyAuth
X-API-Key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/tx/execute" \  -H "Content-Type: application/json" \  -d '{    "actionId": "string",    "signature": "string"  }'
{  "ok": true}

The calling party's settled trades (either role) GET

Only settled trades are recorded — a trade in flight is not listed until it settles.

Prepared ledger actions awaiting this party's signature GET

Every action waiting on this party's signature: the ones calls returned (a quote, an accept, a deposit accept, a withdrawal), plus any the desk queued itself for a trade you accepted (an allocation the accept could not queue at once, or a fresh one replacing an action that expired or was lost to a desk restart). Sign what is listed here after a lost response, and keep draining it while a trade of yours settles. Each action is a `SignActionDto` with a `hash` (base64 bytes of a Canton prepared-transaction hash): sign the RAW bytes (not the base64 text) with the party's Ed25519 key and call `POST /tx/execute`. An action leaves this list when it executes, when it expires (10 minutes), or when its flow dies first (a quote's actions go with the quote at its `validUntil`). Always empty for parties the desk signs for.