Skip to main content
POST
Create Transactional Email
Create a transactional email template with exactly one content source: prompt for Sequenzy-generated transactional blocks, blocks for finished caller-supplied content, or html for preserved/imported markup. Prompt-created templates default to disabled; explicit HTML or blocks retain the compatibility default of enabled. Generated transactional footers omit unsubscribe treatment.

Request

string[]
Company label names, trimmed and deduplicated. Missing names are created in your company. Each name must be non-empty and at most 255 characters. Send [] to clear assignments. Omit to start without labels. null, blank names, and non-string entries are rejected.
string
required
Transactional email name.
string
API slug used when sending by slug. If omitted, Sequenzy generates one from the name.
string
Email subject line. Required with html or blocks; optional with prompt, where it overrides the generated subject.
string
Optional preview override. With prompt, the generated preview is used when this field is omitted. Pass null to suppress preview text.
string
Natural-language request for Sequenzy to generate branded transactional blocks with a footer that omits unsubscribe treatment.
string
Optional generation style. Valid only with prompt. Pass designed or plain to force the designed or plain-text email style; other values are freeform prompt guidance. Defaults to your company’s email style preference (designed unless you chose plain text).
string
Optional generation tone. Valid only with prompt.
string
Raw HTML body. Provide either html or blocks, not both.
array
Sequenzy email blocks. Provide either blocks or html, not both. Put block styling under styles; top-level style keys like backgroundColor, backgroundOpacity, textColor, textAlign, borderColor, borderWidth, and borderRadius are normalized into styles.
boolean
Whether this transactional email can be sent immediately. Defaults to false with prompt and true with explicit html or blocks.

Responses

Label names appear in the response’s transactional.labels array. Invalid label names return 400; invalid label types return 422. Retrying the same label replacement does not duplicate company labels or send an email. After an uncertain update response, read the template before retrying. Label-only updates preserve email content and translations. Insufficient API-key permissions return 403. Label support uses the existing transactional write permission; no additional label scope is required.