Elixpo Mails

Elixpo Mails Docs

Delivery logs

Every send attempt produces a delivery log entry, so you can see exactly what happened to each email — and replay or debug failures.

Statuses

  • sent — accepted by the sender's mailbox.
  • failed — a downstream send failure; see the error field.
  • suppressed — the recipient was unsubscribed; the send was skipped (a successful no-op).
  • sending — in flight.

What each log records

  • Recipient — the to address.
  • Template — which template was rendered.
  • Webhook — the endpoint the trigger came through.
  • Error — the failure reason, when status is failed.
  • Merged variables — the exact variables object used for the send.

Idempotency

Pass an idempotency_key in the trigger body to dedupe retries. A repeated request with the same key resolves to the original delivery instead of sending again — safe to retry on network errors.

Reuse keys for natural events

Derive the key from the event that caused the send (e.g. the order ID or a password-reset token) so accidental double-fires collapse to one email.

Unsubscribe