Email API integrations

Your app knows when.
NoticeAPI sends it.

Choose the shortest working path from your framework, runtime, billing event, or auth provider to a customer email.

Get API keyRead the quickstart
  • REST API
  • Typed Node SDK
  • SMTP relay
One observable pathFrom product event to recipient result
  1. 01TriggerYour productAuth, billing, or app event
  2. 02DispatchNoticeAPIREST, SDK, or SMTP
  3. 03ResultYour workflowRecipient state or webhook
Test first, verify the sender, then move the same workflow live.
Use the stack you have

A hands-on guide for the tools in your product.

ReactNext.jsNode.jsTypeScriptStripeSupabaseAuth0
Build

Send straight from your server code.

Keep the server boundary, framework conventions, and deployment model you already trust.

Framework

Next.js

Send from App Router handlers, Server Actions, auth callbacks, and background jobs.

Open the guideRuntime

Node.js

Use the typed SDK in Express, Fastify, queues, workers, and long-running services.

Open the guideSMTP

Nodemailer

Keep the transport you already have and relay through implicit TLS on port 465.

Open the guideTemplates

React Email

Compile typed React templates, then send the rendered HTML through NoticeAPI.

Open the guide
Connect

Turn product events into email.

Connect billing and identity events to the messages customers expect next.

Billing

Stripe

Send receipts, invoices, and failed-payment notices from verified webhook events.

Open the guideIdentity

Supabase Auth

Route verification, magic-link, and password-reset email through NoticeAPI SMTP.

Open the guideIdentity

Auth0

Use NoticeAPI as the provider behind Auth0 verification and password-reset messages.

Open the guide
Shared production path

Every guide finishes in the same place.

The framework changes. The path from a tested outcome to a verified sender and observable delivery does not.

Read the testing guide
  1. 01Test the outcomeUse simulator recipients for delivered, bounced, complained, and suppressed paths.
  2. 02Verify the senderPublish SPF and DKIM records, then confirm the sender is verified.
  3. 03Ship the workflowSend through REST, the Node SDK, or SMTP from the integration you chose.
  4. 04Return the resultRead the recipient outcome or forward a signed webhook into your app.
Start with one message

Choose the first workflow.

Start in the simulator, then move the same request to a verified production sender.

Get API keyOpen simulator docs