API Changelog
Next-gen API v1.29
Contact filters
- The
jsonfilter is now documented in full: its operators, howandandorcombine and nest conditions, and worked examples. It applies toGET /lists/{list_id}/contacts,GET /lists/{list_id}/segments/{segment_id}/contactsandPOST /lists/{list_id}/exports, and to thejsonfield of the segment, tag and interest requests. - In a query string,
jsonis one JSON-encoded value, for examplejson={"and":[{"tagged":{"tag":"vip"}},{"like":{"email":"a*"}}]}, URL-encoded. queryandfiqlare deprecated in favour ofjson. They still work.
Fixes
- A contact filter on an unknown link now answers
400instead of500. PATCH /brands/default/domains/defaultwith an empty bounce domain now answers422instead of500.PATCH /templates/{template_id}now applies an emptycontent.subject.- A campaign created from a blueprint now keeps the blueprint's
jsoncontent. GET /v2/emails/{email_id}answers400EMAIL_NOT_FOUNDwhen the email can't be read, and rendering an email that can't be found answers400"Email not found".GET /formspages its listing again, and reads basic forms whose dates are missing or unreadable.- Campaign dates are converted with the 2026 time zone rules.
Last modified on