Send transactional email
Send a transactional email via the public API. Automatically creates/updates contacts.
Documentation Index
Fetch the complete documentation index at: https://docs.mailglyph.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API Key authentication. Secret keys (sk_*) are required for all endpoints except /v1/track. Public keys (pk_*) only work with the /v1/track endpoint for client-side event tracking. Workspaces can have multiple active keys, and sender-domain operations enforce per-key domain scope when configured.
Body
Recipient email(s). Can be a string, an object with {name, email}, or an array of either. Maximum 50 recipients per request.
Sender email address (requires verified domain). Required unless using a template that has a 'from' address configured. Can be a string (e.g., "[email protected]" or "My App <[email protected]>") or an object with {name, email} (e.g., {name: "My App", email: "[email protected]"}).
Email subject (required if no template)
Email body HTML (required if no template)
The plain text version of the message.
If not provided, the body will be used to generate a plain text version. You can opt out of this behavior by setting value to an empty string.
Template ID to use for this email. When provided, uses the template's subject, body, from, and reply-to settings. You can override these by explicitly providing subject, body, from, or reply fields in the request. Template variables are populated from the data field.
Sender display name (alternative to using from.name)
Whether recipient is subscribed to marketing emails. Defaults to false for transactional emails.
Optional template variables. Choose Empty object if you do not want to send any example preset keys.
- Example object
- Empty object
{
"resetLink": "https://example.com/reset/abc123"
}Custom email headers
Reply-to address
Email attachments (max 10 attachments, 10MB total)
10
