Events

Every webhook body, and the payload of every item in the event list, is the same envelope. data is the full current state of the object the event is about, never a delta, so you can always apply the latest version you hold.

{
  "schemaVersion": "1.0",
  "sourceEventId": "evt_01K7Q3ZVC1J3K5M7P9R1T3V5X7",
  "eventType": "ca.action.created",
  "objectType": "CORPORATE_ACTION",
  "objectId": "ca_01K7Q3ZVB8M2N4P6R8T0V2X4Z6",
  "version": 1,
  "stream": { "type": "TOKEN", "id": "7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d" },
  "sequence": 142,
  "occurredAt": "2026-10-20T13:50:22.452Z",
  "publishedAt": "2026-10-20T13:50:24.768Z",
  "environment": "sandbox",
  "changedFields": [],
  "data": { "sourceCaId": "ca_01K7Q3ZVB8M2N4P6R8T0V2X4Z6", "version": 1, "tokenId": "7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d", "...": "the whole object" }
}

Field	What it is
`schemaVersion`	The envelope’s shape. `1.0` today; see Versioning
`sourceEventId`	One per event. Deduplicate on it. It is the `eventId` of the event list. The delivery’s `svix-id` header is a different id, the message id, so always read `sourceEventId` from the body
`eventType`	What happened, `ca.<resource>.<action>`. Switch on it; it is also what endpoint filters and the `eventTypes` query use
`objectType`	What `data` is: `CORPORATE_ACTION`, `RESTRICTION` or `TOKEN`
`objectId`	The `sourceCaId`, `restrictionId` or `tokenId` of the object
`version`	The object’s version this event publishes. Apply by it
`stream`	The token stream the event was published on; `id` is the `tokenId`
`sequence`	Strictly increasing within the stream, with gaps. Order by it
`occurredAt`	When the change was recorded
`publishedAt`	When the event was published
`environment`	`sandbox` or `production`. Refuse an event from the wrong one
`changedFields`	Dot paths that differ from the previous version; empty on a first version
`data`	The whole object. For a corporate action, plus the stream’s `tokenId`

Event types

`eventType`	`objectType`	Meaning
`ca.action.created`	`CORPORATE_ACTION`	A corporate action was announced, version 1. May be `PRELIMINARY`
`ca.action.updated`	`CORPORATE_ACTION`	Terms completed or changed in the normal course, for example a rate confirmed or dates set
`ca.action.corrected`	`CORPORATE_ACTION`	Previously published data was wrong; `correctionReason` says why
`ca.action.postponed`	`CORPORATE_ACTION`	Key dates moved, or cleared with status `POSTPONED` until new ones are set
`ca.action.cancelled`	`CORPORATE_ACTION`	Withdrawn by the issuer or Securitize, or replaced by another. Terminal
`ca.action.status_changed`	`CORPORATE_ACTION`	The lifecycle moved: election open, entitlements fixed, settling
`ca.action.completed`	`CORPORATE_ACTION`	Executed; `settlement` attached. Terminal
`ca.restriction.added`	`RESTRICTION`	A trading restriction started
`ca.restriction.updated`	`RESTRICTION`	Its details changed, for example `expectedEnd` or `reasonText`
`ca.restriction.removed`	`RESTRICTION`	It ended. Terminal for that restriction, and the only way one ends
`ca.token.updated`	`TOKEN`	Token reference data changed: name, asset identifiers, status

The names follow the domain.resource.action convention of Securitize’s other webhook families; every type of this API is in the ca domain. New types can be added in minor versions: apply data by version for an eventType you do not know, and keep going. The request body of each event, with an example, is in the API reference under Webhooks.

Delivery guarantees

At least once. The same event can arrive more than once, with the same sourceEventId.
Possibly out of order. Deliveries run in parallel; order by stream.id and sequence.
Within 60 seconds of publication is the target; a scenario in sandbox arrives within seconds.
Retried for 72 hours on anything but a 2xx within 10 seconds, then marked failed and kept 90 days for replay and recovery.

Publication timing

Securitize’s target is ca.action.created within one business day of confirming an announcement, and the urgent events, cancellations, postponements and Securitize-originated restrictions, as soon as possible. Final commitments are in the commercial agreement.

Get started

Guides

Concepts

Help

API reference

Event types

Delivery guarantees

Publication timing