Skip to main content
POST
Render an email message as HTML without sending it. The HTML is the same as the body of a preview email. Accepted variable fields depend on the parent’s type:
  • Campaign accepts contactProperties.
  • Workflow accepts contactProperties and eventProperties.
  • Transactional accepts dataVariables.
Supplying a field the parent cannot reference results in a 400 Bad Request error. A variable without a value uses its fallback, or shows a missing-value marker as in a preview email. The HTML has no open tracking pixel. As in a preview email, the unsubscribe link opens a page that does not unsubscribe anyone.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

emailMessageId
string
required

The ID of the email message.

Example:

"cle5f7g9h1i3j5k7l9m1n3p5"

Body

application/json
contactProperties
object

Contact property values to render. Accepted for campaign and workflow emails.

Example:
eventProperties
object

Event property values to render. Accepted for workflow emails only.

Example:
dataVariables
object

Transactional data variables to render. Accepted for transactional emails only.

Example:

Response

Rendered email message.

html
string
required

The rendered HTML. For emails made in the editor, it includes the rendered subject in <title> and the rendered preview text.

Example:

"<!doctype html><html>...</html>"