Skip to main content
The Marketing transactional endpoint sends one functional email from your backend using a saved Marketing template. Good examples include:
  • Password resets
  • Receipts
  • Verification codes
  • Account and security notifications
  • A user-requested export
Do not use this endpoint to bypass subscription status for newsletters, promotions, or announcements. Those belong in Broadcasts or Workflows.

​
Behaviour

​
Prerequisites

  1. A paid Marketing plan
  2. An active Marketing domain
  3. A template whose sender uses that domain
  4. An account API key
Create API keys under Settings → API keys. Store the key only in a server-side secret manager.
Never put an account API key in browser JavaScript, a mobile app bundle, a public repository, or an HTML form.

​
Find the template UUID

Open Marketing → Transactional and choose a template. The request builder displays its UUID, subject, sender, and the current API request details. You can also copy the UUID from:
  • The template list
  • The template editor title bar

​
API reference

The API reference is the source of truth for the endpoint, authentication, request schema, responses, errors, and language examples.

Marketing transactional API

Open the API reference and select the Marketing transactional endpoint.
The Marketing page in the dashboard can also build a request from a selected template and its merge fields.

​
Merge fields

JetEmail replaces the template’s merge tokens with values supplied by your application. The dashboard request builder scans the selected template and identifies the values it expects. Review every value before sending, especially URLs, verification codes, names, dates, and amounts. See Personalisation & merge fields for template-side guidance.

​
Limits and fair play

Paid Marketing plans have no monthly message limit for Marketing transactional email. The fair-play policy applies, and the endpoint has a rate limit.

​
Production handling

  • Set a reasonable HTTP timeout
  • Follow the status codes and error schema in the API reference
  • Record the returned message identifier with your application event
  • Queue traffic and retry only retryable failures
  • Use your own idempotency guard where the application event must send once
  • Never include secrets in merge values or application logs
  • Keep reset and verification URLs short-lived
  • Monitor the result in Marketing → Logs
Marketing transactional email is separate from the general JetEmail transactional API. Use it when you want a saved Marketing template and its sender configuration.