SendSend documentation
SendSend is a REST API for email: password resets and receipts, newsletters to your audience, and mail you receive. Send it, then see exactly what happened to every message.
Base URL: https://api.sendsend.email. Requests and responses are JSON. Every request needs an API key, and every key belongs to one project.
How it fits together
- Organization: your account, team and billing. Agencies keep one organization for all clients.
- Project: one app or one client. It has its own API keys, domains, templates, webhooks and daily limit. Projects are either test (nothing is delivered) or live.
- Domain: the address you send from. Live mail needs a verified domain.
Where to start
- Quickstart: send a first message with a test key.
- Add and verify a domain: needed before you send real email.
- Webhooks: learn when a message is delivered or bounces.
- API reference: every endpoint, with examples. The same description is available as an OpenAPI file.
- WordPress plugin: send all WordPress email through SendSend.
- Audiences and broadcasts: email your contacts, to everyone or to a segment.
- Receive email: an address for your project, or your own domain.
- Zapier, Make, n8n, Supabase and Clerk: connect the tools you already use.
202 does not mean delivered. A successful send response means the message was safely queued. Delivery, bounces and complaints arrive afterward, as webhooks and in the message timeline.