Skip to main content
Every list endpoint supports filtering through query parameters in the form filter[<field>][<operator>]=<value>. Multiple filters combine with AND.
The endpoint reference lists each filterable field and the operators it accepts. The tables below show the most each field type allows, and a field can accept fewer. A filter on an unknown field, an operator the field does not accept, the same filter sent twice, or more than one of eq, ne and in on one field returns 400 BAD_REQUEST, so a typo never returns the unfiltered list. An empty in list matches nothing.

Operators by field type

Common patterns

Filter by date range

Filter by multiple values

Search by substring

Exclude ended subscriptions

Combine with pagination

Pass the same filter parameters with each page when paginating:
Malformed filter syntax returns 400 BAD_REQUEST and an invalid value returns 422 UNPROCESSABLE_ENTITY, each with a message naming the offending parameter. See Errors for the full envelope.