Documentation

Send a message

The POST /v1/emails contract, fields and response semantics.

Accepts a message and returns 202 only after the message, per-recipient deliveries, idempotency key and outbox event commit in one transaction.

FieldTypeNotes
fromstringMust be on a verified domain in your workspace
tostring | string[]Max 50 recipients per message
subjectstringRequired, ≤ 500 characters
reply_tostringOptional Reply-To address; display name allowed. Use this instead of a custom Reply-To header
html / textstringAt least one required; html ≤ 1 MiB
streamstringtransactional (default) or marketing
tagsobjectString key/value pairs, echoed in events
headersobjectAdditional headers. From, To, Subject, Date, Message-ID and Reply-To are set by the API
template_idstringResolve subject, html and text from a saved template
template_dataobjectValues for {{variable}} placeholders
cc / bccstring | string[]Additional recipients; BCC is omitted from headers
scheduled_atstringRFC3339 or natural language like "in 2 hours"
topicstringPer-message topic; contacts opted out are failed
attachmentsarrayUp to 20 files, 40 MiB total; base64 content or public HTTPS path, optional content_id for inline CID
test_modebooleanAccept and record without attempting SMTP delivery
202 Accepted
{"id": "msg_2f9c…", "status": "accepted", "recipients": 1}

The dashboard compose screen at /app/send supports the same CC/BCC, attachments, topic and scheduling fields without an API key. Fetch state with GET /v1/emails/{id} orGET /v1/messages/{id}/deliveries.

Need the full API surface? OpenAPI 3.1.