Email Logs API Guide & Recipient Event Telemetry

GET/api/v1/emails/:id

Fetch a send by the id returned from send/batch. Includes the per-recipient delivery timeline: every provider event we've ingested for the message.

curl https://www.noticeapi.com/api/v1/emails/EMAIL_ID \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx"

Response

{
  "id": "5f0c1a...",
  "from": "billing@acme.com",
  "to": ["user@example.com"],
  "subject": "Your receipt",
  "status": "accepted",
  "deliveryStatus": "delivered",
  "provider": "noticeapi_email_api",
  "messageId": "0f83...",
  "createdAt": "2026-07-02T18:04:11.000Z",
  "events": [
    { "type": "delivered", "recipient": "user@example.com",
      "detail": "OK", "at": "2026-07-02T18:04:14.000Z" }
  ]
}
FieldTypeDescription
statusstringqueued | sending | accepted | failed | uncertain. Scheduled records also show scheduled, sent, or canceled.
deliveryStatusstring | nullLatest stored state or recipient outcome: queued, sending, delivered, bounced, spam, quarantined, suppressed, failed, or uncertain.
events[].typestringdelivered, opened, clicked, bounced, spam, quarantined, suppressed, failed, unsubscribed.

Open and click events appear when tracking is enabled by the sending domain defaults or a per-send tracking override. Tracking is off by default.