- The endpoint returns
202 Acceptedafter the email send is created and queued for delivery. - Provide either
htmlortext; you can send both, but at least one is required. - Recipient addresses are normalized and deduplicated. Any address present in
tois removed frombcc. - The final combined
toandbccrecipient count may not exceed50. - If a recipient email matches an existing contact in the workspace, the resulting message is linked to that contact automatically.
Send Email
Queue an email for background delivery from a sendable workspace address. The API returns a send group identifier and the final recipient counts after normalization.
Delivery Behavior
How sending, normalization, and recipient linking work
POST
/v1/workspaces/:workspace/emailsQueue a developer email send
Path parameters
workspacestring Required ID of your workspace
Request body
fromstring Required Sendable email address configured for the workspace
subjectstring Required Email subject line
htmlstringHTML email body. Required when `text` is not provided.
textstringPlain text email body. Required when `html` is not provided.
toarray Required Primary recipient email addresses. At least one recipient is required.
Show Object Properties
bccarrayOptional blind-copy recipients. Final unique `to` plus `bcc` count cannot exceed 50.
Show Object Properties
reply_tostringOptional reply-to email address
headersobjectOptional custom email headers
Show Object Properties
Validation Notes
Common request constraints to account for
- The
fromaddress must belong to a sendable address configured in the workspace. headersmust be an object of header names to string values, not an array.- Header names may only contain letters, numbers, and hyphens.
- Header names and values may not contain line breaks.
- The
X-LEADPUSH-SEND-IDheader is reserved and cannot be overridden.