Prompt

How do I set up Notify with a verified sending domain?

Technology / API Platforms4 observationsLast seen Sep 10, 2026

Latest observation

Sep 10, 2026PerplexityWeb search: on

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

  1. 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
  2. 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.com or mail.yourcompany.com). plainenglish
  3. 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

  4. 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.
  5. Send email using the verified domain
    Once verified, use your domain in the from field 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 from address 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=none and 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.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (4 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.