# Next-gen API v1.30

## Suppressed emails

`POST /suppressed-emails` accepts `{"emails": [...]}` to add up to 1000 patterns in one request, beside `{"email": ...}` for one. A list is validated whole before anything is written. Repeated patterns and patterns already suppressed are skipped, and the response reports what was added and what was skipped. The operation is now rate limited per account.

## Segments

- A segment created with `query` or `fiql` now answers `json`: the equivalent `json` filter, when one can be derived from the stored query, or `null`.
- Creating a segment with `query` or `fiql` and no `json` no longer stores a `json`.

## Fixes

- A `json` filter with a non-numeric link ID answers `400`.
- `POST /lists/{list_id}/exports` answers `400` for a `json` filter on an unknown link or campaign.
- Another account's DKIM key answers `400` "DKIM record not found".
- Rate limits count concurrent requests from different accounts separately.
- `GET /forms`: `filter=name==X` selects only the forms named exactly X, a raw `+` in `sort` is accepted, and sorting, filtering and paging are consistent.
- `PATCH` of a basic form with an invalid body answers `422` instead of `500`.
- An embedded form's CSS no longer restyles the host page.
