How sending works

Understand the Publiq pipeline: from the API call to the inbox, with queue, rendering, delivery and observability events.

When you call emails.send, Publiq accepts and queues the email and immediately returns an id with status queued. The actual send happens asynchronously — your request is not blocked waiting for the provider.

The pipeline

  • Accept — the API validates the request (sender, recipient, template) and creates the message with status queued.
  • Render — the body is assembled: template + variables, open/click tracking and a signed unsubscribe link.
  • Deliver — the provider sends; the status becomes sent then delivered (or bounced).
  • Engagement — opens and clicks become opened / clicked events.
  • Observability — every transition becomes an event available via Webhooks and in the dashboard.

Because it is asynchronous, a 202 queued means "accepted", not "delivered". Use Webhooks to know the final result of each email.

How sending works — Publiq Docs