Email infrastructure
Email your product can rely on
An HTTP API and an SMTP endpoint for the mail your application has to send. Requests match Resend's format, so code you already have — including code an assistant wrote for you — works after changing one URL.
Ten messages free, no card. Enough to verify a domain and watch one arrive.
curl -X POST https://pigeonatlas.com/v1/emails \
-H "Authorization: Bearer pa_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"from": "Prodavnica <hello@mail.prodavnica.rs>",
"to": ["kupac@example.com"],
"subject": "Narudžbina #4471 je potvrđena",
"html": "<p>Hvala na narudžbini.</p>",
"text": "Hvala na narudžbini."
}'
The response comes back as soon as the message is queued, so a slow recipient never slows your request.
Built around the parts that actually decide whether mail arrives
Your DKIM key, not ours
We generate a key for your domain and sign under our own selector. Your DNS points only at us, so changing what runs underneath never asks your customers to edit a record.
Newsletters cannot delay a password reset
Bulk and transactional mail are dispatched by separate processes that never read each other's work. A broadcast to fifty thousand people does not put a single reset behind it.
Dead addresses stop at the door
A hard bounce or a spam complaint suppresses an address permanently, and the check runs when you submit rather than before delivery — so it never enters the queue at all.
You can see exactly what was sent
Every message is archived as the bytes that actually went out, searchable by recipient, with its full delivery history beside it.
Already using something else?
Moving from Resend is a base URL and a key. The guide covers the one step people skip — bringing your suppression list — which is also the step that costs them.
On deliverability
All posts-
Don't send newsletters from your transactional domain
Complaints about a newsletter follow the domain that sent it. Share one domain and a campaign can cost you password resets.
-
Two DMARC records is worse than none
A domain with two DMARC records has no DMARC policy at all. It looks configured, reports nothing, and enforces nothing.
-
SPF, DKIM and DMARC, explained by what actually breaks
Three records, three different jobs. Here is what each one does, and the specific ways each one silently fails.
Verify a domain, get a key, send
The free allowance is there to prove it works for you before anything is decided.
Create an account