Email Templates

Templates

Save a reusable subject + body once, then send it with per-recipient values. Templates are tenant-scoped and managed with the same cm_ key (email permission).

Create a template

POST /api/v1/email/templates

The template object returns id, name, subject, html, text, default_sender, default_reply_to, tags, is_active, created_at, updated_at. The id is a UUID.

PUT /templates/{id} takes the same fields, all optional, and applies only the ones you actually send.

Two write-time rejections apply to both create and update, and both come back as a 422 with a plain string detail:

• A control character in subject, default_sender or default_reply_to. Those values are rendered into raw headers at send time.
• A body or subject that references {{ contact.anything }}. Nothing can populate that namespace, so the reference would render as an empty string and ship a broken message. Pass the value in params instead. The same reference on a send is rejected as 422 unresolvable_template_vars.

Using a template on send

Add templateId and params to POST /api/v1/email/send:

# Create a template
curl -X POST https://api.callmissed.com/api/v1/email/templates \
  -H "Authorization: Bearer cm_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "receipt",
    "subject": "Your receipt, {{ params.name }}",
    "html": "<p>Hi {{ params.name }}, your order {{ params.order_id }} is confirmed.</p>",
    "default_sender": "Acme Ops <donotreply@acme.com>"
  }'

# Send from it - send-call fields override the template
curl -X POST https://api.callmissed.com/api/v1/email/send \
  -H "Authorization: Bearer cm_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "templateId": "9d0f8b3a-1c2e-4a5b-8f7d-6e2a1b0c9d4e",
    "to": ["Ada <customer@example.com>"],
    "params": { "name": "Ada", "order_id": "1043" }
  }'

The send returns the same 202 Accepted body as any other send. See Send Email.

• Override rule. The template's subject / html / text are the base; an explicit subject / html / text / from / reply_to on the send wins. default_sender / default_reply_to fill in only when the send omits them.
• Substitution. {{ params.KEY }} (and nested {{ params.a.b }}) are replaced from params; a missing key renders empty. Values placed into the HTML body are HTML-escaped. This is plain variable substitution and not a programming language: no logic, loops, or expressions, and it can only read the params you pass. A substituted value is inserted once and never re-scanned, so a param whose value itself contains {{ ... }} is not expanded again.
• Inline substitution. params also renders placeholders in a subject / text / html you pass directly on the send, so you can use {{ params.KEY }} with no templateId at all. Whichever value is actually used, yours or the template's, is rendered exactly once.

Note: unlike Brevo's integer template id, a CallMissed templateId is a UUID.

Manage templates

# List (limit / offset supported)
curl "https://api.callmissed.com/api/v1/email/templates?limit=50&offset=0" \
  -H "Authorization: Bearer cm_your_key"

# Fetch one
curl https://api.callmissed.com/api/v1/email/templates/9d0f8b3a-1c2e-4a5b-8f7d-6e2a1b0c9d4e \
  -H "Authorization: Bearer cm_your_key"

# Partial update - only the fields you send change
curl -X PUT https://api.callmissed.com/api/v1/email/templates/9d0f8b3a-1c2e-4a5b-8f7d-6e2a1b0c9d4e \
  -H "Authorization: Bearer cm_your_key" \
  -H "Content-Type: application/json" \
  -d '{"subject": "Your updated receipt, {{ params.name }}", "is_active": true}'

# Delete (204)
curl -X DELETE https://api.callmissed.com/api/v1/email/templates/9d0f8b3a-1c2e-4a5b-8f7d-6e2a1b0c9d4e \
  -H "Authorization: Bearer cm_your_key"

Common template failures

409 and 404 on the template routes use a plain string detail with no reason; template_not_found and template_inactive on a send are nested under detail. See Limits, Quotas & Errors.