Returns every ledger update in ledger order across all record types, and is
the endpoint to use for audit and for incremental synchronisation. The
typed endpoints are narrower views over the same events. The response is a
superset of the Ledger API v2 GetUpdatesResponse envelope —
CreatedEvent/ArchivedEvent entries carry their native field names alongside
this API's own chainId and envelope wrapper.
ledgerOffset is a monotonically increasing opaque cursor. Persist the
highest one you have processed and pass it as ledgerOffset[gt] to resume,
which is more reliable than filtering on a timestamp because two events can
share one commit time.
This is a genuinely tier-agnostic feed. Being native, it returns events from
every Daml application on the participant, not only the ones the other tiers model.
Two consequences worth planning for.
The volume is dominated by housekeeping. Most events on a participant are routine
Canton Coin housekeeping, chiefly a single validator-liveness record that is rewritten
roughly hourly, while DTCC registry activity is a small share. Filter on
packageName before anything else — it is far more effective than filtering on
templateId or interfaceId alone.
There is no normalised eventType — templateId and interfaceId are the type.
Canton itself has no such concept, and a fixed list of event types could never be
exhaustive: a new application on the participant produces events with template ids
this API has never seen. templateId is always present and always precise, so it is the
disambiguator where two applications define the same entity name — the token
standard's Holding interface and the DTCC registry's concrete Holding being the
case you will actually hit; filter on interfaceId when you want every implementation
of an interface regardless of concrete template. instrumentId and amount are
absent on events that carry no quantity, such as credentials and delegations.
Record families you can expect to see, for orientation only — not a filterable
field. Use packageName/templateId/interfaceId to actually filter;
this table only helps you recognise what you're looking at.
| Package | Template families |
|---|---|
| DTCC registry | Holding, TransferOffer, ExecutedTransfer, mint/burn requests and offers, rejection records, compliance/registrar delegations, allow-list entries, party credentials, participant service/onboarding requests |
| Canton Token Standard (CIP-0056/V1 and CIP-0112/V2) | Holding interface view, TransferInstruction interface view |
Canton Coin (splice-amulet) | Amulet/holding, transfer instructions, transfer pre-approvals (and proposals), validator licenses, validator reward coupons, validator rights, top-up state, wallet-app install |
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
This endpoint is served under the
nativetier. A request is refused with403if thenativetier is not licensed for your account.
For usage guidance, see Audit & Incremental Sync.
