Skip to main content
POST
Preview a rendered template
Renders the template’s subject and body with merge fields filled, exactly as a send would, without sending or changing anything. It is a POST only because the contact travels in the body, so a retry is safe and it takes no Idempotency-Key.

Example

Things to know

  • Without contact, the template is rendered against a sample contact: Jordan Rivera, VP of Operations at Northwind Logistics, with no custom fields. Every {{custom.<label>}} field therefore comes back in missing_fields.
  • missing_fields lists the merge fields that rendered empty because the contact has no value for them: the gaps a real send to that person would have.
  • Misspelled fields are not listed. A field the renderer does not know, such as {{frist_name}}, stays in the output exactly as written. Read the rendered subject and body_html as well.
  • Any team member can preview any template. It counts toward the Sequencer writes rate limit, because it is a POST.

Authorizations

x-api-key
string
header
required

Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.

Path Parameters

id
string
required

24-character template id.

Body

application/json
user_id
string
required

The team member this call acts as. Must be an active member of the team the API key belongs to. A 24-character hexadecimal ID.

Example:

"507f1f77bcf86cd799439011"

contact
string

A contact on your team to render against (404 if not found). Without it, a sample contact is used: Jordan Rivera, VP of Operations at Northwind Logistics, with no custom fields. A 24-character hexadecimal ID.

Response

The rendered subject and body.

subject
string
required

The rendered subject.

body_html
string
required

The rendered HTML body. Substituted values are HTML-escaped.

missing_fields
string[]
required

Merge fields, as written in the template, that rendered empty for this contact.