Events
Numonic ingests SES delivery events and makes them queryable. Every delivery, bounce, complaint, and suppression action is recorded as an event tied to the originating send ID. Events require JWT authentication.List events
Request
All events:Query parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
type | string | — | Filter by event type: Delivery, Bounce, Complaint, or Suppression |
limit | integer | 50 | Results per page. Max 100 |
page | integer | 1 | Page number |
Response 200
Event fields
| Field | Description |
|---|---|
id | Unique event ID |
email_id | ID of the send this event belongs to. Use with GET /api/v1/send/:id/status to get the full send record |
event_type | Type of event — see event types |
event_timestamp | When the event occurred |
recipient | The specific email address this event applies to |
bounce_type | Present on Bounce events. Permanent or Transient |
bounce_subtype | Present on Bounce events. SES bounce subtype (e.g. General, NoEmail) |
complaint_type | Present on Complaint events. ISP feedback type (e.g. abuse, fraud) |
Event types
| Type | Description |
|---|---|
Delivery | Email was accepted by the recipient’s mail server |
Bounce | Email was rejected. Permanent bounces (hard bounces) automatically add the address to suppression. Transient bounces are temporary failures |
Complaint | Recipient filed a spam complaint. Address is automatically added to suppression |
Suppression | Recipient was on your suppression list and was filtered out before the send went out |
Correlating events with sends
Each event’semail_id maps to the id returned when you created a send:
