Skip to main content

Send a single email

Send a single transactional email. Returns 202 Accepted with the email ID.

Request body

* At least one of html or text is required.
The total number of recipients across to, cc, and bcc must not exceed 50.

Example

Response — 202 Accepted

If any recipients are on the suppression list, the response includes them:
For scheduled emails, scheduledAt is included in the response:

Batch send

Send up to 100 emails in a single request. Each email in the array uses the same schema as a single send.

Response — 202 Accepted

If some emails fail validation, those entries will include an error object. Successfully validated emails are still queued.

Scheduling

Set the scheduledAt field to an ISO 8601 datetime to delay delivery:
scheduledAt must be at least 1 minute in the future. Dates in the past are rejected.

Idempotency

To prevent duplicate sends (e.g. on network retries), include an idempotency key:
Or pass it in the body as "idempotencyKey": "order-confirmation-12345".
  • Duplicate requests within 24 hours return the original response.
  • Keys must be unique per organization and ≤ 255 characters.
  • Use meaningful keys like order-confirmation-{orderId} or welcome-email-{userId}.

Attachments

Add up to 10 attachments per email. Content must be Base64-encoded.

Retrieve email status

Response includes the full email object wrapped in data, with current status, sender/recipient details, timestamps, and associated events:

List emails

Response