Skip to content
send.io
All posts
Reliability

Accepted, delivered, read: three different things

An API success response is the start of an email’s journey. Model the later events so support and engineering can see what happened.

Accepted, delivered, read: three different things — illustrated Sendio guide
On this page

Separate request handling from delivery

A successful API request tells you what the provider accepted, according to that provider’s contract. It does not automatically tell you where the email ended up. HTTP 202, for example, means a request was accepted for processing, not that processing is complete.

Keep your own application event ID alongside the provider’s message ID. When someone asks about a missing invitation, this connection lets you trace the invitation event to the request and its later delivery notifications.

An application queues a message, an email provider accepts the request, and a receiving server accepts or rejects the mail.
Track application, provider, and receiving-server events separately.

Name the states precisely

A delivery event commonly means a receiving mail server accepted the message. That does not establish inbox placement or prove that a person read it. Check the exact event definitions from your provider before turning them into customer-facing labels.

  • Queued: your application has stored work to send.
  • Accepted: the provider accepted the send request.
  • Delivered or bounced: a later delivery outcome reported by the provider.
  • Complained: a recipient complaint was reported; handle it separately from delivery.

Make the history useful to support

Show a timeline with timestamps, stable IDs, and a short explanation of each event. Prefer ‘accepted by the receiving server’ to a vague green ‘success’ badge. Keep internal error details available to the team without placing sensitive payloads in routine logs.

Delivery and engagement should be separate records rather than one status that every event overwrites. A useful message history explains what the system knows and leaves room for what it cannot observe.

Further reading

MDN: HTTP 202 Accepted

AWS: Email event notifications