Events

Every webhook body, and the payload of every item of GET /webhook-events, is the same envelope:

{
  "eventType": "investor.minting.completed",
  "eventId": "investor.minting.completed-3697998",
  "timestamp": "2026-05-07T16:24:27.512Z",
  "data": { "id": "3697998", "tokenId": "d1dbb6b6-3bda-48f2-b86e-c87610db1ae1", "...": "the step" }
}

Field	What it is
`eventType`	What happened, `investor.<resource>.<action>`. Switch on it; it is also what the `eventType` filter of `GET /webhook-events` takes
`eventId`	One per event, the same on every retry and resend. Deduplicate on it. It is the event type followed by the id of what the step is about. The delivery’s `svix-id` header is a different id, the message id
`timestamp`	When Securitize sent the event, ISO 8601 UTC. The time of the step itself is in `data`
`data`	The step. Its fields depend on `eventType`

In data, a field with no value is left out, never sent as null: uetr on a deposit with no wire reference, tokenIssuanceId on a transfer. The endpoints, by contrast, always return every field, with null when there is no value.

Event types

`eventType`	`data.id` is	Meaning
`investor.deposit.processed`	The deposit	A cash movement was recorded on your account: your deposit, its liquidation when it is applied to tokens, or a withdrawal or refund
`investor.minting.completed`	The token issuance (`tokenIssuanceId`)	Tokens were minted to you, for a subscription or a reinvested distribution, with the cash movements behind them
`investor.transaction.processed`	The transaction	A token movement on your account was recorded on chain: an issuance, or the transfer that starts a redemption
`investor.redemption.pending`	The redemption	Your transfer was matched to the open redemption: a request on record, not yet approved
`investor.redemption.confirmed`	The redemption	Securitize approved the redemption: its cash amount and payment method are fixed
`investor.payout.initiated`	The redemption	The cash left Securitize. Not sent for payment methods that complete in one step
`investor.payout.completed`	The redemption, or the distribution of a reinvestment	The cash reached you, or a distribution was reinvested

The names follow investor.<resource>.<action>. New types are added as the API covers more of your activity: store an eventType you do not know and keep going. The request body of each event, with examples, is in the API reference under Webhooks.

The order of a subscription

investor.deposit.processed       cash received                data.id = deposit, direction = deposit
investor.deposit.processed       cash applied to the tokens   data.id = another deposit id, direction = liquidation, same amount
investor.minting.completed       tokens minted                data.id = tokenIssuanceId, depositMovements = the deposit and its liquidation
investor.transaction.processed   issuance recorded on chain   data.tokenIssuanceId, data.txHash = the mint's txHash

Each cash movement sends its own investor.deposit.processed: one for your deposit, and one for its liquidation. A subscription funded by several deposits sends a pair per deposit and one minting for all of them. The issuance transaction and the minting are recorded independently: either can arrive first. See Reconcile a subscription.

The order of a redemption

investor.transaction.processed   your transfer recorded on chain   data.txHash, processType = primary-redemption or redemption-requested
investor.redemption.pending      matched, on record                data.id = redemption, data.txHash = the transfer's
investor.redemption.confirmed    approved, cash amount fixed       data.id = redemption
investor.payout.initiated        cash sent (some methods only)     data.id = redemption, sourceTransaction.txHash = the transfer's
investor.payout.completed        cash received                     data.id = redemption

See Reconcile a redemption.

A reinvested distribution

A distribution you reinvest sends investor.payout.completed with paymentMethod reinvest and the cash value of the distribution, then investor.minting.completed with source reinvest and no deposits, and investor.transaction.processed with processType reinvest. The minting and the transaction share tokenIssuanceId; the payout carries no id that links it to them, so match it by tokenId and time.

Delivery guarantees

At least once. The same event can arrive more than once, with the same eventId.
Possibly out of order. Steps recorded by different parts of Securitize arrive independently.
No failure events. A step that does not complete sends nothing. When an expected webhook does not arrive, check the deposit or transaction, and GET /webhook-events.
Retried for about a day on anything but a 2xx within 15 seconds, then marked failed. Every webhook sent stays readable through GET /webhook-events.

Get started

Guides

Concepts

Help

API reference

Event types

The order of a subscription

The order of a redemption

A reinvested distribution

Delivery guarantees