All webhook events follow a consistent structure:
| 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 |
context values returned, refer to the events endpoint.
Event topics
Nomos currently supports the following webhook events:
| Event Topic | Context Fields | Description |
|---|
subscription.created | subscription, lead (optional) | A new subscription has been created |
subscription.confirmed | subscription | A subscription has been confirmed - can happen multiple times when the start date changes |
All event topics follow the format resource.action (e.g.,
subscription.created, invoice.finalized). The context object contains IDs
of relevant resources that you can use to fetch additional details via the
API.
