Admin Login
HomeGuidesAPI ReferenceChangelogBlockdaemon Main Docs
Log In
Guides

Operation Lifecycle

Idempotent operation ids, status polling, and the event stream

Idempotent submission and status tracking

Every asynchronous Vault API start route accepts an OperationID. That id is the handle for retries, status, and audit. The same rules apply to transfers, sponsorship, Canton enrollment, and the other start routes.

OperationID matches ^[a-zA-Z0-9-]{1,96}$.

Idempotent submission

Send the id in the start body.

curl -s -X POST "https://<wallet-host>/api/cwp/operations/start/makeTransaction" \
  -H "authorization: <api-key>" \
  -H "content-type: application/json" \
  -d '{
    "OperationID": "payout-2026-10-21-acme",
    "CAIP19": "eip155:1/slip44:60",
    "Asset": "ETH"
  }'

The example shows the operation id. A live transfer also sends source, destination, and amount. The start response echoes OperationID.

Submit the same id again only with the same intent:

  • The same id and the same intent leave the original operation in place. A retry after a timeout does not open a second operation.
  • The same id with a different intent is rejected. Choose a new id for a changed payment.

Store the id before you call start. If the HTTP response is lost, poll status with that id.

Status tracking

GET /api/cwp/operations/id/{operationID}/status returns the current state.

curl -s "https://<wallet-host>/api/cwp/operations/id/payout-2026-10-21-acme/status" \
  -H "authorization: <api-key>"

Status moves through the pending states, then ends at Succeeded or Failed.

StatusMeaning
Pending initializationThe operation is being prepared.
Pending confirmationThe initiator still has to confirm.
Pending approvalApprovers still have to approve.
Pending executionQuorum is complete and execution has not started.
ExecutingPolicy Nodes are signing or the wallet is broadcasting.
Pending signatureA signature is still outstanding.
SucceededThe operation finished. Result holds the outcome, such as a transaction id or signed payload.
FailedThe operation stopped. ErrorDetails includes ErrorCode and the status where it failed.

Poll until Succeeded or Failed. Approval can sit in Pending confirmation or Pending approval until a person or an automated approver acts.

Event stream

GET /api/cwp/events upgrades to a WebSocket on the same host. Messages are hints. They do not include the full status body, and they are not replayed.

Read status once when the socket opens, so an operation that already finished is not missed. On each operation_status_update, call GET .../status again.

Repeat the type query to limit the stream. Omit it to receive every type.

TypeWhat it signals
operation_status_updateAn operation changed status.
approval_requestedThe authenticated user has an approval waiting.
approval_cancelledA pending approval was cancelled.
approver_onboardedAn approver finished onboarding.

Order is not guaranteed. Status from the GET is the record to trust.

A browser WebSocket that cannot set the authorization header can pass the header value as the second subprotocol entry, unpadded base64url, with the first entry cwp.v1.

🗣️We Are Here to Help!

Please contact us via email or support chat if you encounter an issue, bug, or need assistance. Don't forget to include any relevant details about the problem. To request a wallet form and Institutional Vault Approver form, please click here or contact our sales team.


Did this page help you?