| Field | Type | Description |
|---|---|---|
id | string | Unique event identifier (starts with evt_) |
timestamp | string | ISO 8601 timestamp when the event was created |
topic | string | Event type identifier (e.g., subscription.created) |
context | object | Event-specific data containing relevant resource IDs |
topic field tells you what kind of event arrived. Topics are always shaped as resource.action — the resource that changed (e.g., subscription) and what happened to it (e.g., created).
To keep payloads small and predictable, context carries only the IDs of the resources involved. When you need the current state of one of those resources, fetch it from its own API endpoint (for example, GET /subscriptions/{id} for a subscription).