Sign in
Email Templates

Create an email template

Creates a Liquid email template. Variables are auto-extracted when omitted.

post/email_templates

Headers

Idempotency-Keystring

Optional opaque, unquoted key for safely retrying the same logical request. Keys must contain 1 to 255 letters, numbers, hyphens, or underscores. Generate a unique UUID v4 for each operation and reuse it only when retrying that operation with the same request. Invalid headers—including duplicate, empty, malformed, or overlong values—return 400 with error code 10015. A request already in progress with the same key returns 409; reusing the key with a different request returns 422. Only successful responses are replayed, for up to 24 hours. Do not include sensitive data in the key.

Request body

namestring required

Letters, numbers, spaces, hyphens, and underscores only.

subjectstring nullable

Liquid template subject.

html_bodystring nullable

Liquid template HTML body.

text_bodystring nullable

Liquid template text body.

variablesstring[]

Template variables. Auto-extracted from subject/body fields when absent.

strict_variablesboolean

Per-template strict variable-validation setting. Defaults to false for backward compatibility. When true, a send or render that is missing a variable marked required: true in variable_schema fails with 422 naming the variable. Missing optional variables never fail; their schema default (when set) is applied to the render.

autoescapeboolean

Per-template HTML autoescaping setting. Defaults to false for backward compatibility. When true, the rendered html_body HTML-escapes each Liquid expression's output at the output boundary (after its filters run, before concatenation with literal template markup). Input values are never mutated and subject/text_body are never autoescaped. The boundary escape is idempotent: HTML entities already present in the output (e.g. from an explicit escape filter) are preserved, so an explicit escape/escape_once is never double-escaped, and markup introduced by any later filter in the chain is still escaped.

variable_schemaobject nullable

Structured variable requirements. Required variables cannot define defaults; invalid combinations return 422. This is independent of the legacy variables array. On render with strict_variables enabled: required variables must be supplied as non-empty values — absent, null, empty string, empty object {}, and empty array [] all fail with 422 naming the variable, while present values such as false and 0 pass (they are present, not empty). Optional variables fall back to their default when absent.

Response

Template created.

Changes