Send a message
Enqueue a message for delivery. Provide either template (send a
stored template) or content (inline raw content) — never both.
Returns 202 immediately; the message is dispatched asynchronously.
Authorizations
API key with an sk_live_ or sk_test_ prefix.
Headers
Optional caller-supplied key to make a send safely retryable. A repeat request with the same key (within the same workspace and environment) returns the original send instead of creating a duplicate. Recommended for all sends so client retries never double-send.
Body
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
Template slug to send.
Recipient (email address, phone number, or device token).
Optional explicit version pin. Defaults to the latest version in test mode and the current published version in live mode.
x >= 1email, sms, push, web-push Variables interpolated into the template.
Caller-supplied tags/IDs. Values must be string, number, or boolean.
Optional ISO-8601 timestamp to schedule the send for later. Must be
in the future and within 30 days. When provided, the send is
accepted with status: "scheduled" and dispatched at that time.
Email-only. Cc recipients applied at send time.
Email-only. Bcc recipients applied at send time.
Email-only. Reply-To address applied at send time.
Email-only. Per-send attachments — not stored on the template.
Email-only. Optional From address override (bare address — put the
display name in fromName). Defaults to the provider connection's
address. On managed sending it is honored only when the address is
on the workspace's verified sending domain.
Email-only. Optional From display name override, rendered as
Name <address>. Defaults to the provider connection's from name.
Must not contain control characters or angle brackets.
128Response
Message accepted and queued for delivery.