Email sending, receiving and everything around it
Eight parts of one product. Each page below covers something you can use on its own, and all of them run on the same API, the same dashboard and the same sending pipeline.
Email API
Send transactional email over one REST call: idempotent sends, batches, scheduling, attachments, templates and a delivery timeline for every message.
Read moreWebhooks
Every delivery, bounce, complaint, open and click posted to your endpoint, signed with a timestamp, retried on failure and replayable from the dashboard.
Read moreDomains
Add a domain, publish the generated record set and send from it. A 2048-bit DKIM key per domain, a custom return path, and verification that runs on its own.
Read moreReceiving
Receive email at your own domain. A signed webhook names every message; read its headers, text and HTML, and fetch attachments behind signed links.
Read moreTemplates
Write an email once, publish a version, and send it by ID or alias with typed variables. Every send records the exact version it used.
Read moreBroadcasts
An audience you own: contacts with typed properties, segments, topics people subscribe to, and broadcasts sent through the same pipeline as your other mail.
Read moreAutomations
Workflows that run per contact: start on a custom event or a segment change, wait, branch, and send. Every run pins a version and is inspectable.
Read moreFor AI agents
An MCP server, a setup skill, Markdown at every docs URL and typed SDKs, so an assistant can set Rasket up and send for you with no key in the prompt.
Read more
Built in, not bolted on
Four things that arrive with the first request rather than with a later plan.
Idempotent sends
Put an Idempotency-Key on a send and a retry within 24 hours returns the first response instead of a second email. A different payload under a key you have already used is refused rather than guessed at.
Automatic suppressions
A permanent bounce or a spam complaint puts the address on your team's suppression list. Later sends to it are skipped and recorded, not attempted.
Request logs
Every call made with your team's credentials is kept with its method, status, latency and request ID, so an error you are holding leads straight to the call that produced it.
Rate limits with headers
Ten requests a second per team, with the ceiling, what is left in the bucket and the seconds until it refills on every response, so you can slow down before you are refused.
Each one is written up in full in the docs: idempotency keys, suppressions, request logs and rate limits. The pricing page says what each plan includes.
Start sending this morning
Sign up, verify a domain and send your first email in minutes.