Notify
Sign in

Sandbox vs Production

Guided inbox test and API rehearsal first, then verify a domain for production sending.

Notify separates early exploration from production sending so you can integrate without burning deliverability.

Guided dashboard test

New accounts can send one real plain-text email to their signup address from hey@test.notify.cx via the dashboard checklist. That send counts toward usage and shows in Recent activity. It does not unlock custom from addresses.

API rehearsal (/api/email/send/test)

Rehearse the HTTP contract without delivering:

curl -X POST https://notify.cx/api/email/send/test \
  -H "Content-Type: application/json" \
  -H "x-api-key: $NOTIFY_API_KEY" \
  -d '{
    "to": "you@example.com",
    "subject": "API rehearsal",
    "message": "Hello from Notify",
    "from": "noreply@your-verified-domain.com"
  }'

These requests log a TEST row and do not hit SES or your monthly quota. The sandbox page only validates JSON payload shape.

Production sending

Production sends use:

POST https://notify.cx/api/email/send

(rewrite alias: /api/send-email; /api/public/v1/email/send permanently redirects)

New accounts are sandbox_only until you verify a domain. Without a verified domain, production sending returns DOMAIN_VERIFICATION_REQUIRED.

Recommended path

  1. Create an account and generate an API key from Credentials or the dashboard checklist
  2. Send yourself a guided test email (or skip)
  3. Add and verify your domain
  4. Send production email with to, from, subject, and message
  5. Watch logs and optional webhooks

Next steps