Skip to main content
POST
cURL
Guide: Sending email

Authorizations

Authorization
string
header
required

Authorization: Bearer . An application key (tk_live_, tk_test_) has full access, which covers every product and any product added later, or custom access, chosen when the key is created: one or more of the scopes verify:check, verify:send (includes verify:check), notifications:read, notifications:send (includes notifications:read), email:read, email:send (includes email:read), notifications:templates (includes notifications:read). No key made on the API keys page holds notifications:templates, full access included: the three template writes answer such a key 403 insufficient_scope. A connected app's key holds it. A call outside the key's access answers 403 insufficient_scope and names the scope it needs in the WWW-Authenticate response header. A partner key (tk_partner_) always has full access. Whatever its access, a key is a server-side secret.

Headers

Idempotency-Key
string

A 1 to 128 printable-ASCII-character key you generate, scoped to your API key, as on WhatsApp messages. Replaying the same key returns the original 202 unchanged, with the response header Idempotent-Replayed: true: nothing is sent or charged again. A send that fails with 502 releases the key.

Body

application/json
to
string
required

One recipient: a syntactically valid e-mail address. One recipient per call.

subject
string
required

The subject line, 1 to 255 characters.

from
object

{ "name": "…", "address": "…" }. address must be on a verified domain of this application, any local part. Omitted, name is the domain's default from name and address its default local part (no-reply unless changed) on the application's verified domain.

html
string

The HTML body. Give html, text or both; together they are at most 512 KiB.

text
string

The plain-text body, shown by clients that do not render HTML. Give html, text or both.

reply_to
string

Where replies go: any valid address, on your domain or not.

reference
string

Your own reference (order id, event id), 1 to 64 printable characters. Echoed back, carried by the webhooks, and searchable on Email → Messages in the console.

Response

Accepted

id
string
status
string
from
object
to
string
subject
string
reference
string
price_halalas
integer
created_at
string<date-time>
Last modified on October 13, 2026