Sending domains
Email API for Multiple Sending Domains
NoticeAPI is built for products, workspaces, and client senders that need separate verified domains without separate email stacks. Add domains, send from approved addresses, and keep REST, SDK, SMTP, webhooks, and suppressions on one API.
curl -X POST https://www.noticeapi.com/api/domains \
-H "Cookie: noticeapi_session=..." \
-H "Content-Type: application/json" \
-d '{ "domain": "send.acme.com" }'Plan-based domain counts
Free includes 1 verified sending domain. Pro includes 10, then extra domains are $1/domain/month up to the self-serve limit.
DNS verification
NoticeAPI generates ownership, SPF, DKIM, and DMARC records so production senders are authenticated.
Sender identities on first use
Once a domain is verified, local parts and display names can be used naturally in API sends.
No DNS redo on upgrade
Capacity expands with the account; upgrades do not require rebuilding sender DNS for existing domains.
Domain model
Built for many products without many email accounts.
Use multiple verified senders from one account and one API. Plan changes expand capacity without making existing domains redo DNS.
1 domain
Enough to start verified-domain production email with one sender.
Pro10 included
A practical default for builders running several products or environments.
Usage$1/domain
Extra domains stay visible on the bill instead of forcing an immediate tier jump.
Custom50+ domains
Domain-heavy accounts can talk through sender topology without rebuilding DNS.
How it works
From test send to production traffic.
Add the domain
Create a sending domain in the portal and copy the generated DNS records.
Publish DNS
Add the ownership, SPF, DKIM, and recommended DMARC records at your DNS provider.
Verify readiness
NoticeAPI checks each record and marks the domain verified when production sending is allowed.
Send for each product
Use the same API key and endpoints while sending from each verified product or client domain.
Trust
Many domains, one safety model
Additional domains do not bypass sender checks. Each production sender still uses domain verification, ramp limits, suppressions, logs, and the deliverability autopilot.
Implementation links
Build with the shipped docs.
FAQ
Questions developers ask before switching email.
How many domains can I add?
Free includes 1 verified sending domain. Pro includes 10, then extra domains are $1/domain/month up to the self-serve limit. Custom covers domain-heavy accounts.
Do I need to redo DNS when I upgrade?
No. Existing verified domains stay configured. Higher plans expand limits and quota without changing the DNS you already published.
Can each domain send broadcasts and transactional email?
Yes, if the domain is verified and the send respects the right path: transactional messages through send or SMTP, audience updates through broadcasts and automations.
Start in the sandbox, then send from a verified domain.
Free includes simulator testing and 3,000 emails per month. Real sending on Free needs operator activation plus a verified domain; Pro adds more volume, domains, contacts, automation runs, REST attachments, and visible usage billing.