Skip to main content
Fetch a single message by id, including its full delivery lifecycle — the ordered list of events from queued through delivery, bounce, open, or click. GET /v1/emails/{id} Works for both directions. For outbound messages the events trace the send lifecycle; for inbound messages it reflects receipt. To read the rendered body, use GET /v1/emails/{id}/body.

Path parameters

string
required
The message id returned by a send, batch item, reply, or list.

Request

Response

200 OK — the message with its events lifecycle.
200 OK

Fields

string
The message identifier.
string
The sender address.
string[]
The recipient addresses.
string | null
The subject line.
string
The current status — e.g. queued, sent, delivered, bounced, complained.
string
outbound or inbound.
string
When the message was created (ISO 8601).
object[]
The ordered lifecycle — each event has a type and a timestamp; engagement events may carry extra detail.
404. not_found if no message with that id exists for this account. Ids are scoped to your account — you can never read another tenant’s message.