PlatformXeDocs
Get API Key

Email Overview

Transactional email with multi-provider fallback, retry queue, and delivery tracking.

The PlatformXe Email Service sends transactional emails reliably using a multi-provider fallback architecture. If the primary provider fails, the service automatically routes through backup providers with circuit breakers to ensure delivery.

How it works

  1. Your application sends a ready-to-render email payload to the PlatformXe API.
  2. PlatformXe selects the active provider and dispatches the email.
  3. If the provider fails, the circuit breaker trips and the request is routed to the next provider in the fallback chain.
  4. If all providers fail, the email enters a persistent retry queue with exponential backoff.
  5. After 7 failed attempts, the email moves to the dead-letter queue for manual inspection.

PlatformXe is a dumb pipe for email. Your application owns template selection, merge logic, and branding. PlatformXe receives pre-rendered HTML and dispatches it.

Key features

  • Multi-provider fallback — automatic failover between providers with circuit breakers
  • Persistent retry queue — exponential backoff ensures transient failures are retried
  • Dead-letter queue — unrecoverable failures are captured for inspection
  • Delivery tracking — subscribe to delivery events via webhooks
  • Idempotency — use the x-idempotency-key header to prevent duplicate sends

API scope

All email endpoints require the messaging:send scope on your API key.

Endpoints

MethodPathDescription
POST/api/v1/messaging/email/sendSend an email
GET/api/v1/messaging/queue/statsGet retry queue statistics
POST/api/v1/messaging/queue/processManually trigger queue processing

Next steps