Email API Quickstart: Send Your First Message in 5 Minutes

Create a key, verify one sender domain, and copy the send call. Your workspace and first project already exist.

Copy the API key

Sign up free, then create an API key under API keys. It starts with ntc_ and is shown once.

Verify the sending domain

Add send.yourapp.com under Domains. Install the DNS records with the Cloudflare flow or copy them to your provider, then click verify. DNS propagation time depends on the provider.

Send the customer email

Replace the sender and recipient, then run the request. Use an idempotency key tied to the app event so a retry cannot send the same receipt twice. Production sends return 202 with an id to inspect.

terminal
curl -X POST https://www.noticeapi.com/api/v1/email/send \
  -H "Authorization: Bearer $NOTICEAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1042-receipt" \
  -d '{
    "from": "Acme <receipts@send.yourapp.com>",
    "to": "customer@example.com",
    "subject": "Your receipt from Acme",
    "text": "Thanks for your order. Receipt #1042 is ready."
  }'

Open the delivery timeline

Every send returns an id. Fetch it to see per-recipient outcomes:

curl https://www.noticeapi.com/api/v1/emails/EMAIL_ID \
  -H "Authorization: Bearer $NOTICEAPI_API_KEY"

Optional: exercise a failure state

When you need to test bounce, complaint, or webhook handling, use the sandbox sender and a simulator recipient. Simulator sends never reach a mailbox or use quota.

optional simulator request
curl -X POST https://www.noticeapi.com/api/v1/email/send \
  -H "Authorization: Bearer $NOTICEAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "demo@sandbox.noticeapi.com",
    "to": "bounced@simulator.noticeapi.com",
    "subject": "Bounce test",
    "text": "Watch the delivery timeline."
  }'

Free includes one project, 3,000 Transactional emails, one domain, and sandbox testing each month. It has no marketing contacts or automations; add a card through the secure Stripe setup flow before production sending. Paid plans add inbound receiving, larger audiences, automations, and REST attachments.