Routing follows the send-only key or mailbox key you authenticate with. You cannot
choose a provider or delivery group inside an individual send request.
Prerequisites
- A team with sending access.
- A send-only key or mailbox key with
email.send. - Enough team balance for the messages you send.
- A verified custom domain, unless you are testing with the shared domain.
Send one email
201 Created with a queued message_id.
Send a batch
Send up to 100 messages in one request. The response reports each message by its input index.Useful options
| Option | Use it for |
|---|---|
cc, bcc | Add more recipients. Each list can contain up to 100 recipients. |
reply_to | Direct replies to a different address. |
return_path | Set the envelope sender for bounce handling. |
custom_headers | Add custom X-* headers to the outgoing message. |
attachments | Attach files as base64 content. |
Idempotency-Key | Safely retry a request without sending twice. |
Error handling
Check theok field. If it is false, read error.code, error.message, and meta.request_id.
Related guides
SMTP sending
Use SMTP when an existing tool only supports SMTP delivery.
Attachments
Add files to HTTP send requests.
Idempotency
Make send retries safe with
Idempotency-Key.Sending accounts
Connect providers and control routing before you send.