Events & reliability
Event payloads
Understand the customer event envelope and business transitions behind subscriptions.
Common envelope
Deliveries identify event_id, event_type, event_version, correlation_id, payload and occurred_at. Read type and version together. Preserve the raw body for verification before parsing. The example shows envelope fields, not a complete type-specific payload.
{
"event_id": "<event-id>",
"event_type": "trade.accepted",
"event_version": "v1",
"correlation_id": "<correlation-id>",
"payload": {
"trade_id": "<trade-id>"
},
"occurred_at": "<RFC3339 timestamp>"
}Customer lifecycle events
| Event | Interpretation |
|---|---|
| quote.expired | Quote expiry; obtain new terms before acceptance. |
| trade.accepted | Instruction accepted, not settled. |
| trade.funding_required | Funding is needed before execution. |
| trade.funded | The funding transition has been recorded. |
| trade.settlement_processing | Settlement processing has begun. |
| trade.settled | The workflow has recorded confirmed settlement. |
Subscription scope
Subscribe to event types enabled for your workflow. Payload detail depends on type and version; read the canonical resource for its full state. Do not infer FX execution, a return or reversal from an unrelated event. Book events and private order reads are separate interfaces.