Email Components
Preview Default Footer
Review affected emails and rendered HTML before applying your default footer.
POST
Preview Default Footer
You can preview a footer update without saving it. Send
The
blocks (a nonempty email
block array), optional name and nullable description, and required application
with scopes and optional includeCustomized. An empty scope array previews only
the default. The supported slot is footer.
200 response includes success, application.token, application.counts,
application.affected, and application.skipped. Each item has scope, kind,
id, and name; skipped items also have reason. With renderPreview: true,
renderedPreview contains footerHtml, samples with beforeHtml and afterHtml,
and a preview limitation note. By default you receive up to one sample per selected
category. Supply sample: { id, kind } for a particular affected email version.
Personal keys require workspace admin access. Keys need emails:write, selected
category write scopes, and ab_tests:write for sequences or campaigns, matching
application permissions. Invalid blocks or slots return 400, invalid credentials
return 401, missing permissions return 403.
Malformed request shapes, such as missing required fields or invalid scope values,
return 422. Unexpected rendering or database failures return 500; transient database
unavailability may return 503.
Apply with Set Default Email Component
using identical inputs and previewToken. Preview does not modify content or send emails.