Test in sandbox

Sandbox publishes no real corporate actions. Instead, one endpoint runs scripted scenarios on any of your tokens, so you can exercise your webhook handler, the event list and the state queries end to end, in minutes.

What sandbox has

Your tokens: sandbox CETs linked to your account, one per chain deployment. GET /tokens lists them; use any of them below.
Real market status. A token’s marketStatus follows the real underlying market, so outside US market hours you read CLOSED with PRE_MARKET or POST_MARKET, as in production.
A webhook endpoint registered by your Securitize contact, with its signing secret. Point it at your sandbox handler.
Scenarios that create corporate actions marked as sandbox tests. They are never executed: no dividend is paid, no multiplier changes.

Trigger a scenario

curl -X POST "$BASE/sandbox/events" \
  -H "Authorization: Bearer $ACCESS_TOKEN" -H "content-type: application/json" \
  -d '{ "scenario": "CASH_DIVIDEND_LIFECYCLE", "tokenId": "7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d" }'

{
  "runId": "sbx_01K7Q4B1E3G5H7K9M1N3Q5S7V9",
  "scenario": "CASH_DIVIDEND_LIFECYCLE",
  "tokenId": "7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d",
  "steps": [
    { "step": 1, "eventTypes": ["ca.action.created"], "executedAt": "2026-10-20T13:50:18.465Z" },
    { "step": 2, "eventTypes": ["ca.action.updated"], "executedAt": "2026-10-20T13:50:18.702Z" },
    { "step": 3, "eventTypes": ["ca.action.status_changed"], "executedAt": "2026-10-20T13:50:18.940Z" },
    { "step": 4, "eventTypes": ["ca.action.status_changed"], "executedAt": "2026-10-20T13:50:19.177Z" },
    { "step": 5, "eventTypes": ["ca.action.completed"], "executedAt": "2026-10-20T13:50:19.415Z" }
  ]
}

Every step runs at once, in order. The run acts on the asset of the token, so its events are published on every token stream of that asset you hold: with the asset deployed on two chains you receive each event twice, once per stream, with a different sourceEventId and sequence.

The scenarios

Scenario	Events, in order	What it exercises
`CASH_DIVIDEND_CREATED`	`ca.action.created` (`PRELIMINARY`)	A first version, with `paymentAsset` still `null`
`CASH_DIVIDEND_LIFECYCLE`	`ca.action.created` → `ca.action.updated` (confirmed: `changedFields` `dataCompleteness`, `status`) → `ca.action.status_changed` (`ENTITLEMENTS_FIXED`) → `ca.action.status_changed` (`SETTLING`) → `ca.action.completed`	The full path of an automated dividend, `settlement` included
`STOCK_SPLIT_LIFECYCLE`	`ca.action.created` → `ca.action.updated` (confirmed) → `ca.action.status_changed` (`SETTLING`) → `ca.action.completed`	Split terms: `ratio`, `fractionHandling`
`CA_CORRECTED`	`ca.action.created` → `ca.action.corrected`	`changedFields` and `correctionReason`
`CA_POSTPONED`	`ca.action.created` → `ca.action.postponed` (dates `null`, status `POSTPONED`) → `ca.action.updated` (new dates)	Dates cleared, then set again
`CA_CANCELLED`	`ca.action.created` → `ca.action.cancelled`	A terminal version with `cancellationReason`
`CA_SUPERSEDED`	`ca.action.created` → `ca.action.created` (a new id, `supersedesCaId`) + `ca.action.cancelled` (the old one, `supersededByCaId`)	Two objects changing in one step
`RESTRICTION_LIFECYCLE`	`ca.restriction.added` → `ca.restriction.updated` → `ca.restriction.removed` (an `ASSET`-scoped `TRADING_SUSPENSION`)	The token reads `UNAVAILABLE` between the first and the last
`UNKNOWN_CA_TYPE`	`ca.action.created` with a `caType` these docs do not list	Your handler must take it as informational and not fail

What to check after a run

Every step reached your endpoint, signed, and you answered 2xx. Compare with the event list: GET $EVENTS/events?since=<the run's first executedAt> (the webhooks base URL, see Replay and recover) returns the same sourceEventIds.
Order came from sequence, not from arrival. Deliveries are parallel: the ca.action.completed of a lifecycle can arrive before its ca.action.updated. Sort what you received by stream.id and sequence and the scenario’s order appears.
Each object ended in the right state. GET /corporate-actions/{sourceCaId} after CASH_DIVIDEND_LIFECYCLE is version 5, COMPLETED, with settlement; after CA_CANCELLED, CANCELLED with cancellationReason; after CA_SUPERSEDED, the old one is CANCELLED with supersededByCaId set.
A restriction changed the status. During RESTRICTION_LIFECYCLE, GET /tokens/{tokenId}/status reads UNAVAILABLE with reason OTHER and one entry in activeRestrictions; after ca.restriction.removed, it is back to the market’s status. The scenario runs in a second, so read the status from the events rather than by polling.
Duplicates were harmless. Run POST /events/recover over the window and confirm that nothing in your state changed.

Sandbox differences

Scenarios run at once; in production, the steps of a corporate action are days or weeks apart.
Sandbox corporate actions are marked as tests in description and are never executed.
Unknown-scenario requests answer 400; a token outside your account answers 404 TOKEN_NOT_FOUND, as in every other call.

Get started

Guides

Concepts

Help

API reference

What sandbox has

Trigger a scenario

The scenarios

What to check after a run

Sandbox differences