Integrate now
You can start sending emails in minutes.
curl
curl -X POST https://api.rasket.com/emails \ -H "Authorization: Bearer rk_..." \ -H "Content-Type: application/json" \ -H "Idempotency-Key: order-1042" \ -d '{ "from": "Acme <[email protected]>", "to": ["[email protected]"], "subject": "Your order is on its way", "html": "<p>Order 1042 shipped today.</p>" }'What every send gets
Send once, correctly.Know what happened.
The parts of transactional email that are hard to get right, built into every request rather than bolted on after.
Idempotent sends
Send the same request twice within 24 hours and you get the same id back, not a second email. A retry is always safe.
Delivery events
Every email keeps a timeline: queued, sent, delivered, bounced or complained, each with its time.
Verified domains
Each domain gets its own 2048-bit DKIM key and a generated record set to publish. Verification runs on its own.
Signed webhooks
Every event is posted to your endpoints with a signature and a timestamp you can verify with a standard library, and retried if you do not answer.