SMTP
Keep your mail client. Authenticate with TLS and an API Key; public host, port and certificates depend on deployment.
Read integration docsFEATURES
Connect through SMTP or the Email API. Manage verified domains together and share your account’s active plan allowance.
Keep your mail client. Authenticate with TLS and an API Key; public host, port and certificates depend on deployment.
Read integration docsOne recipient, explicit fields, standard HTTP. HTTP 202 means accepted; query status or receive Webhooks for later outcomes.
Read integration docsBUILT FOR MULTI-DOMAIN TEAMS
Stop setting up a separate email service for every project. Verify each sending domain once, keep keys and templates together, and share the quota of your active plan.
Bind the sending domains of your products and client sites. Each domain must pass DNS verification before it can send, and the number of domains is capped by your plan.
Read the domain guideAll verified domains draw on the quota of your account's active plan, with total, daily and hourly limits enforced by the server. Acceptance is not inbox delivery — track the final status through the API or signed webhooks.
Read the SMTP guideManage sending domains for different products together. Each domain needs verification; the actual plan defines the domain limit.
Domains share the active plan allowance, with total, daily and hourly limits. Prices and entitlements come from the actual plan configuration.
Keep your SMTP client or use the standard Email API. Both share domain verification, API Key permissions and quota checks.
Manage subjects, HTML and plain text. Send using template_id and string variables. HTML previews are isolated from the console.
Read integration docsQuery by message_id or receive signed Webhooks. Acceptance is not inbox delivery. Callbacks may retry; verify signatures and deduplicate.
Read integration docsCreate an account, verify a sending domain, and send over standard SMTP or the Email API.