Each operation is documented in full under Endpoints in the sidebar.
Base URL
Requests
Send JSON with aContent-Type: application/json header and authenticate with an API key as a Bearer token:
User-Agent header identifying your integration. This is a server-to-server API: a request with no User-Agent is rejected with 400 missing_user_agent, and a browser-originated request with 403 browser_not_allowed. Keep your API key server-side and never call the API from a browser. Set one explicitly in any HTTP client that does not send a default; curl already does.
Every SDK sends a compliant User-Agent for you. If you are building a CLI, an internal service or a framework integration on top of one, set its user-agent suffix option to your own name/version. It is appended after the SDK’s own token, so both layers stay visible.
To make a send, cancel, or reschedule safe to retry, attach an Idempotency-Key header. It is honored on every write operation.
A send carries either raw content (html and/or text) or a saved template (template_id). See Sending your first email.
Responses
A successful send returns200 OK with the message id and its RFC Message-ID:
message_id is the Message-ID header assigned to the message. Echo it in In-Reply-To and References on a later send to thread replies.
A send carrying scheduled_at returns 202 Accepted instead, with the acknowledgment rather than a message id:
id is the handle for rescheduling and canceling, and it is the email_id the later webhook events carry.
Errors return a compact JSON envelope with the HTTP status mirrored in the body:
X-Request-Id header, generated by the server for that request. Quote it when you contact support about a failed call; it identifies the exact request.
See Errors for every code and Rate limits for throttling behavior. Volume, rate, recipient and message-size ceilings depend on your plan; see Plans & limits.