Approve an email
Mark the newest completed version as approved and usable by blasts and flows. Requires subject, from_name, from_address, and reply_to_email to be set (400 email_missing_required_headers otherwise). 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 ID.
Body
Expected current version.
x >= 1Response
Approved.
Full email object.
Email ID.
Internal name (never shown to recipients).
Lifecycle state.
draft, approved Latest content version number.
Subject line.
Preheader text.
Sender display name.
Sender address. Sending requires a verified domain.
Reply-to address.
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 email (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/emails/{emailId}/content.
API path to fetch the plain-text rendition.