Skip to main content

​
Tags

Attach up to 10 tags of 64 characters to any send. They travel with the message: they are returned on GET /v1/emails/{id}, on every webhook event, and they filter the logs.
Use tags for the things you will search for later: the feature that sent the email, the customer segment, a campaign id. Put per-message identifiers such as an order id in a custom header (X-Order-Id) or in an Idempotency-Key instead.

​
The Logs page

Logs in the dashboard shows every email and SMS, newest first, with search by recipient or id and filters for status, channel, tag and date. Click a row for the full timeline, the rendered subject and body, the error if any, a Resend button and Copy as cURL, which reproduces the request. Bodies are kept for 30 days and then redacted; the timeline and metadata stay.

​
List emails with the API

GET /v1/emails returns the same rows, newest first, cursor-paged. Items are the message object without events.
Pages stay stable while new email arrives, so you can walk the whole history for an export or a reconciliation job. See pagination.

​
The message timeline

Every message carries events, oldest first. Each has a type, an occurredAt and, when useful, a detail object with provider ids, error codes or attempt numbers.