Set a personalized email version
Stores the personalized version of a Personalized Email Asset for one contact. One version per contact per asset; re-posting for the same contact replaces their version. At send time the contact receives their version if it’s ready; contacts without one get the asset’s default email.
Validation on arrival: email must resolve to an existing contact, and html must contain the literal {{unsubscribe_url}} token, contain no other {{…}} tokens, and stay within 500 KB. A version that fails validation is rejected with a reason (visible on the asset’s Activity tab) and the default email sends instead.
Authorizations
Personal Access Token or OAuth 2.1 access token, sent as a bearer credential. READ permission for GET, WRITE for POST/PATCH/DELETE.
Body
ID of the Personalized Email Asset. Copy it from the asset URL (…/assets/email/per-user/<ASSET_ID>/versions) or its How to add versions tab.
The contact's email. Must match an existing contact.
The personalized subject line.
The inbox preview text.
Full HTML of the personalized email. Must include the literal {{unsubscribe_url}} token; no other {{…}} tokens are allowed. Max 500 KB.
Optional ISO-8601 expiry. After this moment the contact falls back to the default email. Omit for a version that never expires.