Transactional email API

Transactional Email API for Password Resets, Receipts, and Product Alerts

NoticeAPI gives product teams a transactional email API for messages your app triggers: password resets, magic links, receipts, account verification, billing notices, product alerts, and security notifications.

Idempotent transactional send
curl -X POST https://www.noticeapi.com/api/v1/email/send \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Idempotency-Key: receipt-1042" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme Billing <[email protected]>",
    "to": "[email protected]",
    "subject": "Your receipt",
    "html": "<p>Receipt #1042 is attached.</p>",
    "attachments": [
      { "filename": "receipt.pdf", "content": "BASE64...", "contentType": "application/pdf" }
    ]
  }'

Idempotency keys

Retry safely with Idempotency-Key. Matching retries return the original send result instead of sending twice.

Templates and attachments

Use stored HTML/text templates with merge variables, or send REST attachments for receipts, invoices, and reports.

Stored email bodies

Sent messages keep subject, text, HTML, and recipient state so support can inspect what happened later.

Per-recipient events

Accepted, delivered, bounced, complained, suppressed, and unsubscribed events are recorded and can be delivered to your webhook.

How it works

From test send to production traffic.

1

Choose the right sender

Use the sandbox sender during development, then send from a verified production domain.

2

Pass an idempotency key

Use an order id, reset token id, or job id so retries do not duplicate important email.

3

Use templates for repeated messages

Create reset, verification, receipt, and alert templates with merge variables your app fills at send time.

4

Handle delivery outcomes

Read the email status endpoint or use signed webhooks to update your product when a message bounces or delivers.

Trust

Transactional first, but still protected

Transactional email does not need an unsubscribe link, but it still benefits from automatic suppressions, delivery timelines, domain verification, and the deliverability autopilot.

Implementation links

Build with the shipped docs.

FAQ

Questions developers ask before switching email.

Can I attach receipts or PDFs?

Yes. REST sends support attachments with base64 content. Production attachments are a paid-plan feature; sandbox and simulator sends can accept them for testing.

Does NoticeAPI support scheduled transactional sends?

No. Today the API processes sends immediately. Use your own queue when you need future delivery.

How do I prevent duplicate receipts or reset emails?

Send with an Idempotency-Key. A retry with the same key returns the original result instead of creating another email.

Start free. Send production after your domain is ready.

Free includes 3,000 production emails per month, a 100/day production cap, and one verified sending domain.