Airmail / Developer guides
FuelPrice and Airmail: a Controlled Email Pilot
An internal case study, not an independent customer endorsement. FuelPrice is a road-trip, fuel-cost and toll-planning product operated by the same owner as Airmail.
Free Developer beta. Verified domain and manual sending approval required.
The integration
FuelPrice integrates through Airmail's REST API. Its partnership domain is verified and routed through durable queued dispatch with a lower-priority partnership traffic class. Ordinary application traffic and partnership traffic have separate policy controls. Airmail also offers SMTP, but this case study does not claim FuelPrice migrated to SMTP.
What has been observed
As checked on 20 September 2026, one individually approved hotel prospect introduction had been accepted and delivered. Ten further prospects were approved but not sent. There were no recorded replies, claims, opt-outs or bounces for the first prospect. One delivery is not evidence of inbox placement, booking uplift or campaign conversion.
What makes the workflow inspectable
Stable REST idempotency, durable per-recipient dispatch and delivery lifecycle records make it possible to separate acceptance from delivery. Message Explorer and analytics are available to inspect the result. Prospect messages use a monitored Reply-To and unsubscribe path. Existing suppressions and explicit operator review remain mandatory; public contact information is not converted into campaign consent.
What is deliberately constrained
The pilot is paused until the operator launches a reviewed daily selection. Limits remain ten new prospects per working day, at least one minute between sends and a 25-message total daily ceiling. At most one follow-up requires a later explicit no-response review. Lower priority protects scheduling capacity, not IP reputation: streams still share one reputation boundary. Broader marketing scale needs separately routable infrastructure, not just a higher quota.
Before your first production message
Start with the free Developer beta. Verify your account, create a workspace and add a domain you control: example.com and mail.example.com are both supported. Publish the records shown in Domains. Merge an existing SPF policy rather than adding another; preserve a valid existing DMARC policy. Create an API key after verification, use the dashboard for one owner-controlled validation, and request production approval. SMTP credentials become available after activation. No repository or SSH access is needed.