Verify an email domain and sender
Email sends from your own domain through Convert's configured delivery infrastructure. You need access to the domain's DNS records and the mailbox used to confirm the Reply-To address. Adding a sending domain does not create a hosted inbox in Convert.
Add the domain
- Open Settings → Channels → Email and select Add domain.
- Enter the root domain, such as
example.com. Do not enter a URL, path, or complete email address. - Choose DNS setup: connect Cloudflare or Vercel using the settings shown, or select Manual DNS to copy the required records.
- Review record status and add only entries marked Not added. A Failed record should be investigated rather than replaced blindly.
- Check setup and wait for the domain to become ready for sending.
Use the exact generated record names and values. DNS entries are specific to your domain. For the displayed MX record, use priority 10 when the provider requests a separate priority. Keep existing website and inbox records intact.
DNS propagation can delay verification. Recheck after your DNS provider has published the records. Never invent DKIM or verification values from an example.
Configure the sender and replies
Add a sender address on the verified domain, choose its display name, and complete the confirmation flow. Configure the mailbox that should receive replies and confirm ownership of that Reply-To address. Replies continue to arrive in your own mailbox.
Choose a default active sender for API requests that omit
sender. An explicit API sender must match an active sender in the same workspace. A sender can remain unavailable if its domain, confirmation, or organisational sending state is not ready.Send email through the API
Select
channel: "email" explicitly. Raw email needs to, subject, and message; optional html is the HTML alternative. A saved email template can supply the subject and body. See single-message requests.123456789{ "to": "[email protected]", "channel": "email", "sender": "[email protected]", "subject": "Your order has shipped", "message": "Hi Ada, your order has shipped.", "html": "<p>Hi Ada, your order has shipped.</p>", "test": true }
Troubleshoot readiness
- Domain pending: verify every required record in the DNS provider, including host-name suffixes and record type.
- Sender unavailable: check active status, domain readiness, and sender/Reply-To confirmations.
- Recipient suppressed: inspect bounce, complaint, or unsubscribe state; changing the sender does not erase suppression.
- Request rejected: check
subject, destination format, allowance, wallet balance, and API errors.