Emails

Every individual message sent — delivery status, opens, clicks, and bounces.

The Emails page is the message-level log: one row per email sent (campaign or API). Each row shows the recipient, subject, delivery state, and engagement (opens, clicks).

Use it to answer "what happened to this specific message?" — trace a delivery, confirm an open, or see why something bounced or was suppressed.

Suppression is automatic

A hard bounce or complaint suppresses that address, so future sends skip it. You'll see the suppression reflected here and on the contact — it protects your domain's reputation without manual cleanup.

Sending to many people from the API

Each API send is one request against your workspace's limit, 10 requests a second by default. A request over the limit is answered 429: that message was not sent and has no row on this page, because nothing queues a refused request for you. If a script sent 1,000 emails and fewer rows are here, the missing ones were most likely refused and not retried.

  • One message to one person (a receipt, a sign-in code): POST /api/v1/email, one request each.
  • Many different messages, or your own list from your own script: batches, up to 100 in one request. No contacts needed.
  • The same content to a list: a campaign, one request for the whole audience, paced for you. It takes a segment, or up to 5,000 addresses inline.

If you loop over single sends anyway, pace the loop under your limit and send every 429 again after its Retry-After. The SDKs and the CLI retry for you; a raw HTTP client does not. Rate limits has the details.

Search docs and guides

Search the docs and product guides.