Skip to main content
POST
cURL
from behavior is highly dependent on your account’s setup!
The sender email configuration depends on your account setup:
  • If you haven’t verified a domain: You can only use Contiguity’s email infrastructure. Simply provide your sender name (e.g. ‘Contiguity’).
  • If you have verified a domain: You can either:
Deprecated: body
Instead, provide top-level html / text properties.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
to
required

Recipient email address(es). Can be a string or array of up to 10 addresses

Example:

"john.doe@example.com"

from
string
required

Accepts: "Example <email@domain.com>" or "Contiguity" or "email@domain.com"

Example:

"Contiguity <no-reply@contiguity.com>"

subject
string
required

Subject of the email

Example:

"Hello, world!"

text
string | null

Text content of the email (preferred over body.text)

Example:

"Hello, world!"

html
string | null

HTML content of the email (preferred over body.html)

Example:

"<p>Hello, world!</p>"

body
object | null

Deprecated: use top-level text/html instead.

reply_to
string | null

Reply-to email address

Example:

"john.doe@example.com"

cc

Carbon copy email address(es). Can be a string or array of up to 10 addresses

Example:
bcc

Blind carbon copy email address(es). Can be a string or array of up to 10 addresses

Example:
headers
object | null

Custom email headers as key-value object

Example:

Response

Send an email

id
string
required
Example:

"req_xxxxxxxxxxxxxxxx"

timestamp
number
required
Example:

1772129047728

api_version
string
required
Example:

"v2026.2.26"

object
string
required
Example:

"response"

data
object
required