How do I start sending app emails with Warmerly transactional email?
Transactional email is for the mail your own app sends to its users: password resets, receipts, sign-in links and notifications. Open the product switcher at the top of the sidebar and choose Transactional email. It has its own sidebar (Overview, Emails, Metrics, Domains, Sending keys, Plan & billing), its own keys and its own billing.
It is a separate product from cold outreach. It sends on separate infrastructure, so the
reputation of your campaigns can never put your password resets in spam. For the same reason,
send app mail from a domain or subdomain (such as mail.yourcompany.com) that you do not use
for cold outreach.
This page is the click-by-click start. The request and response details for developers are in the Transactional email API reference.
Set up in five steps
The Overview page shows a "Get set up" checklist that ticks itself off as you go. When all four of its steps are done it collapses to "Setup complete".
-
Add a sending domain. Open Domains, type the domain or subdomain you will send from (for example
mail.yourcompany.com) and click Add domain. Use one that already receives email, or a subdomain of one: Gmail and Outlook distrust mail from a domain nobody can reply to. -
Publish the DNS records. Click Show DNS records. Copy each record to your DNS provider (the guides for DKIM and DNS records show where). You add three DKIM records, plus a bounce record pair and a DMARC record. There is no record on your root domain: your own SPF and MX are untouched, so your regular email keeps working exactly as it does today.
-
Verify it. Press Verify. DNS changes can take a few minutes to show up, so if some records show Missing, wait and press Verify again. Once verified you can send from the domain, and the button reads Re-check from then on.
-
Create a sending key. Open Sending keys, click Create key, name it (for example "Production") and choose a permission:
- Sending only: can send email. It cannot read your emails or change domains. Use this in your application. It can be limited to one domain.
- Full access: can send, read emails and add or verify domains.
Copy the key when it is shown. It is displayed once and cannot be shown again, so store it somewhere safe. Only workspace owners and admins can create keys.
-
Send your first email. On Overview, use Send a test email: pick the from address and domain, type your own address in To, and click Send test. The email appears under Recent emails. The same page has Send from your code with ready-made snippets.
Send from your code
Send the key as a bearer token in the request header, and add an Idempotency-Key header so a
retried request never sends twice. The endpoint, fields and error codes are in the
API reference. A transactional key (it starts with wm_tx_) works only on
transactional endpoints. It is not the same as the Platform API keys under Settings,
and neither works in place of the other.
Read your results
- Emails: every email you sent, with a status. Search by recipient or subject, and filter by status, sending domain and date range. Click an email to see its Timeline of delivery events. The message body is kept for 30 days, and the rest of the record stays.
- Metrics: volume, delivered rate, bounce rate and complaint rate over 7, 30 or 90 days, for all domains or one.
- Overview: recent emails, a sending-health panel, and a warning if a verified domain starts failing its checks.
- Domains: each domain shows a health checklist with a score, so you can see what to fix.
The statuses are queued (waiting to be sent, retried for up to 24 hours), sent, delivered,
deferred, bounced, complained, failed and suppressed. Their meanings are in the
API reference.
Bounces, complaints and your suppression list
An address that hard-bounces or marks an email as spam is added to your Do not contact list
automatically, and nothing is sent to it again. An email whose recipients are all suppressed is
recorded as suppressed and is not sent.
Watch your Bounce rate and Complaint rate on Metrics. The dashboard states that a sender is reviewed at 5% bounces or 0.1% complaints and can be paused. If sending is paused, the Overview shows "Sending is paused for this workspace" and new sends are refused until it is reviewed. Stop sending to addresses that bounce, check where the list came from, then contact support.
Plan and billing
Transactional email is billed separately from your outreach plan, and one email is one recipient. Under Plan & billing you can see your current plan and this month's use, switch plan, choose monthly or yearly billing, and turn pay-as-you-go overage on or off. Only the workspace owner can change the plan. Overage is opt-in: nothing past your allowance is charged unless you switch it on. Prices, allowances and the free tier are on the transactional email pricing page and in the app, not repeated here. An outreach plan does not include transactional sending, and the reverse is also true.
What is not possible
- You cannot send from a domain you have not verified.
- A sending key cannot be used for campaigns, leads, the inbox or any other Warmerly API.
- Transactional email is not for cold outreach. Use Campaigns for that.
Common problems
A DNS record shows Missing. Copy the host and value exactly. Some DNS providers add your domain to the end of the host automatically, so paste only the part before your domain. Wait a few minutes and press Verify again.
The API answers 403 sending_paused. Sending is paused for the workspace because of its bounce or complaint rate. See the section above and contact support.
The API answers 429. You are past the request rate limit or your plan's allowance. Check Plan & billing, or see Errors & rate limits.
I cannot add a domain. The domain may already be in use elsewhere in Warmerly (for example as a OneMail domain or in another workspace), or you have reached your plan's domain limit.
The email is delivered but lands in spam. A new domain has no reputation yet. Send mail your users asked for first and grow volume over a few weeks, send HTML together with a plain-text part, and read your DMARC reports. See the "Deliverability" section of the API reference.