messages

List the SES event timeline for one message

GET /v1/messages/{id}/events

Auth required messages.view

Returns the full SES event timeline for one message (Send → Delivery/Bounce/Reject/DeliveryDelay, then Open and Click events as recipients interact). Events are sorted ascending by occurred_at. The response is not paginated — a typical message has fewer than a dozen events.

Each event carries type-specific metadata (omitted on Send):

Type	metadata keys
`Bounce`	`bounce_type`, `bounce_sub_type`, `smtp_response`
`Complaint`	`complaint_feedback_type`
`Delivery`	`smtp_response`, `processing_time_ms`
`DeliveryDelay`	`delay_type`
`Reject`	`reject_reason`
`Open`	`ip_address`, `user_agent`
`Click`	`click_url`, `ip_address`, `user_agent`

A message with zero stored events — either unknown to the platform or belonging to another org — returns 404 not_found. Same retention caveat as getMessage: events are kept for up to 365 days.

Path parameters

id string required

SES message id.

Responses

200 Chronological event list (ascending) application/json

401 Missing, malformed, or unknown API key application/problem+json

403 Key lacks the required scope or plan limit violated application/problem+json

404 Resource not found application/problem+json

429 Per-org rate limit exceeded application/problem+json

500 Unexpected server-side failure. The code is internal_error. The request_id field can be quoted to SendOps support to investigate. application/problem+json