Approve an email template
Mark the newest completed version as approved and usable for seeding new emails via POST /v1/emails with template_id. Requires at least one completed generation (409 template_not_ready); unlike emails there is no required-sender-header gate — the default header fields are optional. Pass version as an optimistic-concurrency precondition; a mismatch with the newest completed version fails with 409 approval_version_stale. While a generation is running, an approve without version fails with 409 generation_in_progress; a version-pinned approve still succeeds.
Authorizations
Workspace API key, e.g. Authorization: Bearer tented_.... Create keys in Workspace Settings → API Keys.
Path Parameters
Email template ID.
Body
Expected current version.
x >= 1Response
Approved.
Full email template object.
Email template ID.
Internal name (never shown to recipients).
Lifecycle state.
draft, approved Latest content version number.
How the template was created: upload for API- or hand-created templates, email for templates saved from an existing email.
upload, email Email the template was saved from, when source_type is email.
Default subject line copied onto emails seeded from this template.
Default preheader text for seeded emails.
Default sender display name for seeded emails.
Default sender address for seeded emails. Sending requires a verified domain.
Default reply-to address for seeded emails.
Version that is approved, or null.
Number of content versions (equals current_version).
Whether plain text has been manually overridden.
When the plain-text override was set.
True when HTML changed after a plain-text override, so the override may be stale.
Creation time.
Last update.
Who created the template (API key name or user).
Status of the most recent AI generation, when one exists.
generating, completed, failed API path to fetch the latest HTML, e.g. /v1/email-templates/{templateId}/content.
API path to fetch the plain-text rendition.