Transactional email

One-to-one messages triggered by your application — receipts, password resets, alerts. Sent immediately, logged individually.

Send a message

POST/transactional/send

The minimal send is a recipient, a verified sender, a subject, and an HTML body. Requires a key with the transactional scope.

curl -X POST https://api.inbuzzed.com/api/v1/esp/transactional/send \
  -H "X-Api-Key: ib_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "customer@example.com",
    "toname": "Ada Lovelace",
    "fromemail": "receipts@yourdomain.com",
    "fromname": "Your Brand",
    "subject": "Your receipt for order #1024",
    "body": "<p>Thanks for your order, Ada.</p>",
    "tag": "receipts"
  }'

Request parameters

tostringrequired

Recipient email address.

subjectstringrequired

Message subject. Required unless template is provided.

bodystring (HTML)required

HTML body of the message. Required unless template is provided.

fromemailstringrequired

Verified sender address. Required unless templateis provided (the template's sender is used).

tonamestring

Recipient display name.

fromnamestring

Sender display name.

replytostring

Reply-To address. Must pass the same sender-domain policy as fromemail.

returnpathstring

Bounce address. Must pass the sender-domain policy.

tagstring

Free-form label for filtering the send log and analytics.

variablesobject

Key–value data merged into {{variable}} placeholders in the template or body. Supports nested objects via dot paths.

templatestring

ID of a published template to render instead of subject/body.

templateRecordIdstring

Your workspace template record ID. When provided alongside template, the template is validated against your workspace before sending.

routestring

Optional sending route override.

Send with a template

Design the message once in the template studio, publish it, then reference it by ID. Anything in variables fills the template's {{placeholders}} — see Templates & variables.

curl

curl -X POST https://api.inbuzzed.com/api/v1/esp/transactional/send \
  -H "X-Api-Key: ib_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "customer@example.com",
    "template": "tpl_8f2a...",
    "variables": {
      "firstName": "Ada",
      "order": { "id": "1024", "total": "$49.00" }
    }
  }'

The send log

GET/transactional/log

Every transactional send is logged. Page through the log with ?page=, or export it:

POST/transactional/log/export

The same log is browsable in Dashboard → Log with delivery status per message.