Email templates

Email Templates API for Reusable Product Messages

NoticeAPI templates keep repeated product messages out of scattered string literals. Store the subject and body once, pass variables at send time, and reuse the same template from REST, SDK sends, batch jobs, broadcasts, or automations.

Create and send a template
curl -X POST https://www.noticeapi.com/api/v1/templates \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Password reset",
    "subject": "Reset your password, {{FIRST_NAME}}",
    "html": "<p>Use this code: {{RESET_CODE}}</p>"
  }'

curl -X POST https://www.noticeapi.com/api/v1/email/send \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <[email protected]>",
    "to": "[email protected]",
    "templateId": "tpl_xxxxxxxx",
    "variables": { "FIRST_NAME": "Sam", "RESET_CODE": "123456" }
  }'

Template CRUD

Create, list, update, and delete reusable templates from the API or dashboard.

Subject, HTML, and text

Templates store subject, HTML, and optional plain text, then render variables at send time.

Starter templates

New workspaces can install editable welcome, password reset, and receipt starters.

Works across send paths

Use templates in direct sends, batch sends, broadcasts, and automation steps.

Template safety

Reusable messages with visible mistakes.

Stored templates keep repeated product messages reviewable. Missing variables stay visible, and shared send paths reuse the same approved copy.

Subject

Stored once

Keep the subject, HTML, and text together so every email is easier to review.

Variables

{{TOKEN}} stays visible

Unknown merge tokens remain visible instead of silently becoming blank content.

Starters

Editable defaults

Install welcome, password reset, and receipt starters, then adapt them to your product.

Reuse

Send paths share templates

Direct sends, batch sends, broadcasts, and automations can all point at stored templates.

How it works

From test send to production traffic.

Create the template

Store a reusable subject and body with clear merge tokens such as {{FIRST_NAME}}.

Preview and edit

Use the dashboard editor to inspect rendered HTML with sample variables.

Send by id

Pass templateId and variables to the send endpoint instead of embedding the full body.

Override when needed

Send-time subject, html, or text values can override the stored template part for one message.

Trust

Templates make transactional and marketing email easier to audit

Reusable templates keep receipts, resets, alerts, and lifecycle messages consistent. Unknown merge tokens stay visible instead of silently sending blank content.

Implementation links

Build with the shipped docs.

FAQ

Questions developers ask before switching email.

What happens if a variable is missing?

Unknown tokens remain visible in the rendered output so mistakes are noticeable instead of silently blank.

Can I use templates in batch sends?

Yes. Batch sends can reuse a template and pass variables per message.

Are there starter templates?

Yes. Workspaces can install editable welcome, password reset, and receipt starters.

Start in the sandbox, then send from a verified domain.

Free includes simulator testing and 3,000 emails per month. Real sending on Free needs operator activation plus a verified domain; Pro adds more volume, domains, contacts, automation runs, REST attachments, and visible usage billing.