# Next-gen API v1.29

## Contact filters

- The `json` filter is now documented in full: its operators, how `and` and `or` combine and nest conditions, and worked examples. It applies to `GET /lists/{list_id}/contacts`, `GET /lists/{list_id}/segments/{segment_id}/contacts` and `POST /lists/{list_id}/exports`, and to the `json` field of the segment, tag and interest requests.
- In a query string, `json` is one JSON-encoded value, for example `json={"and":[{"tagged":{"tag":"vip"}},{"like":{"email":"a*"}}]}`, URL-encoded.
- `query` and `fiql` are deprecated in favour of `json`. They still work.

## Fixes

- A contact filter on an unknown link now answers `400` instead of `500`.
- `PATCH /brands/default/domains/default` with an empty bounce domain now answers `422` instead of `500`.
- `PATCH /templates/{template_id}` now applies an empty `content.subject`.
- A campaign created from a blueprint now keeps the blueprint's `json` content.
- `GET /v2/emails/{email_id}` answers `400` `EMAIL_NOT_FOUND` when the email can't be read, and rendering an email that can't be found answers `400` "Email not found".
- `GET /forms` pages its listing again, and reads basic forms whose dates are missing or unreadable.
- Campaign dates are converted with the 2026 time zone rules.
