Skip to main content
Canton items — onboarding, allocations, and transfers, including DTCC and Tradeweb flows — are ordinary Fireblocks transactions. There is no separate Canton resource tree: everything Canton-specific arrives in a cantonDetails object on the transaction, and the same object is what you act on and what you receive. This section covers the three things a Canton integration needs:
  • Read Canton Transactions — list and read Canton activity with the transactions endpoints you already use, and identify what a cantonDetails object is telling you.
  • Canton Transaction Webhooks — the push side. An inbound offer is a status update on a transaction you never created, so a Canton integration is a webhook consumer first.
  • Write Canton Transactions — make a Canton call to act on your own wallet or a contract, or answer an offer to respond to one.
Start with the webhook. Most Canton activity — an inbound onboarding offer, an allocation request — begins as a notification, not as something you polled for.