Application email infrastructure

Airmail

Transactional email infrastructure built for developers. Send through REST or SMTP, verify your domains and follow each message from acceptance to delivery.

Developer beta. No payment to start. Verified domain and manual sending approval required.

REST + SMTPMessage ExplorerProvider-aware queues

Built for application traffic

Airmail separates durable API acceptance from provider delivery capacity, then gives each tenant a verified identity and a traceable message lifecycle.

Verified sending domains

Use a root domain or dedicated subdomain you control, with SPF, DKIM, DMARC and Return-Path verification.

Durable provider queues

Messages remain durable while provider-aware pacing protects delivery from concentrated bursts.

Idempotent sends

Retry the same logical request safely with one stable Idempotency-Key.

Lifecycle visibility

Follow accepted, queued, submitted, delivered, deferred, failed and bounced states.

Tenant isolation

Domains, API keys, usage, messages and suppressions are scoped to one tenant.

Delivery analytics

Understand delivery trends, provider delays and domain health, then drill down to the message that needs attention.

One HTTPS request

Send from your server

Use standard HTTP from any backend. API keys remain server-side and raw keys are shown once.

Explore the API
curl https://api.airmailai.tech/v1/messages \ -H 'Authorization: Bearer am_live_example...' \ -H 'Content-Type: application/json' \ -H 'Idempotency-Key: order-812-confirmation' \ --data '{ "from": {"email": "notifications@example.com"}, "to": [{"email": "customer@example.net"}], "subject": "Your order is confirmed", "text": "We received your order." }'

From domain to delivery

Public accounts enter a controlled onboarding flow. Sending stays approval-gated while identity and DNS checks are completed.

1

Create a workspace

Verify your work email and describe the transactional use case.

2

Verify a domain

Use your root domain or a dedicated subdomain. Publish the DNS records shown.

3

Validate one email

Create a server-side key, then complete the dashboard's controlled first-send step.

4

Request approval

Complete the use-case review before production API or SMTP sending.

Read the FuelPrice pilot case study / Find your framework or migration guide

Build with controlled delivery.

Start your Airmail workspace and prepare a verified sending domain.

Start Free