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 sending-only or sending & receiving custom domain if you send through the managed account, unless you are testing with the shared domain. Sends through your own sending accounts do not need one, because each account already authenticates at its own provider.
Send one email
200 OK 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.200 OK while some messages fail. Check
data.summary.failed, then inspect every item in data.results by index.
Queued items include a message_id; failed items include error details.
Useful options
See the Sending API reference for the full schema.
Error handling
Check theok field. If it is false, read error.code, error.message, and meta.request_id.
429 daily_limit_exceeded before queueing that message. A queued message that reaches a full UTC day waits for the next reset. Wait for the Retry-After period or upgrade to Pro.
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.