Verified sending domains
Use a root domain or dedicated subdomain you control, with SPF, DKIM, DMARC and Return-Path verification.
Application email infrastructure
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.
Airmail separates durable API acceptance from provider delivery capacity, then gives each tenant a verified identity and a traceable message lifecycle.
Use a root domain or dedicated subdomain you control, with SPF, DKIM, DMARC and Return-Path verification.
Messages remain durable while provider-aware pacing protects delivery from concentrated bursts.
Retry the same logical request safely with one stable Idempotency-Key.
Follow accepted, queued, submitted, delivered, deferred, failed and bounced states.
Domains, API keys, usage, messages and suppressions are scoped to one tenant.
Understand delivery trends, provider delays and domain health, then drill down to the message that needs attention.
One HTTPS request
Use standard HTTP from any backend. API keys remain server-side and raw keys are shown once.
Explore the APIPublic accounts enter a controlled onboarding flow. Sending stays approval-gated while identity and DNS checks are completed.
Verify your work email and describe the transactional use case.
Use your root domain or a dedicated subdomain. Publish the DNS records shown.
Create a server-side key, then complete the dashboard's controlled first-send step.
Complete the use-case review before production API or SMTP sending.
Read the FuelPrice pilot case study / Find your framework or migration guide
Start your Airmail workspace and prepare a verified sending domain.
Start Free