Prompt
How do I set up Notify with a verified sending domain?
Latest observation
To set up Notify with a verified sending domain, you add your domain in the Notify dashboard, publish the DNS records it gives you (SPF, DKIM, and usually DMARC), wait for verification, then use that domain in the from field when you send via the API.
Step-by-step setup
-
Create an API key (if you haven’t already)
- In the Notify dashboard, generate an API key.
- Copy it once and store it as an environment variable (e.g.,
NOTIFY_API_KEY) instead of hardcoding it. plainenglish
-
Add your sending domain
- Go to the Domains section in the Notify dashboard.
- Click Add domain (or similar) and enter the domain you want to send from (e.g.,
yourcompany.comormail.yourcompany.com). plainenglish
-
Publish the DNS records Notify provides
Notify will show you specific DNS records to add at your registrar or DNS host. Typically:- SPF record (TXT) – authorizes Notify to send on your behalf.
- DKIM record (TXT) – used to cryptographically sign your outgoing messages.
- DMARC record (TXT at
_dmarc.yourdomain.com) – tells receiving servers what to do if authentication fails. plainenglish
Add all records exactly as shown (don’t modify the values). Propagation can take up to 24–48 hours, though it’s often faster. plainenglish
-
Wait for domain verification
- In the Notify dashboard, the domain status will move from “pending” to “verified” once DNS records are detected and validated. plainenglish
- If it stays pending, double‑check that the TXT records are correct and that there are no conflicting SPF/DKIM records.
-
Send email using the verified domain
Once verified, use your domain in thefromfield of your send request, for example:POST [https://notify.cx/api/email/send](https://notify.cx/api/email/send) Authorization: Bearer YOUR_NOTIFY_API_KEY Content-Type: application/json { "to": "user@example.com", "from": "noreply@yourcompany.com", "subject": "Your password reset", "message": "..." }Production sends with a custom
fromaddress require a verified domain. plainenglish
Recommended baseline for email authentication
For better deliverability and fewer spam issues:
- Ensure SPF and DKIM are live and verified in Notify.
- Add a DMARC policy (start with
p=noneand a monitored inbox) at_dmarc.yourdomain.com. notify
If you tell me your DNS provider (e.g., Cloudflare, Route53, Namecheap), I can outline exactly where to add these records in their UI.
Citations
- https://developers.cloudflare.com/email-service/concepts/email-authentication/
- https://notify.cx/blog/spf-dkim-dmarc-explained-for-developers
- https://plainenglish.io/apis/how-do-i-set-up-notify-with-my-sending-domain-and-api-key
- https://notify.domains/spf-dkim-dmarc-checker-tool/
- https://plainenglish.io/programming/how-do-i-send-transactional-emails-from-an-api
- https://notify.domains/understanding-the-dashboard/
- https://plainenglish.io/apis/how-do-startups-usually-handle-receipts-and-account-emails-without-building-their-own-email-stack
- https://mailtester.com/blog/spf-dkim-dmarc-record-change-monitoring-alerts