Skip to main content
The Everflow API supports two distinct filtering mechanisms depending on the endpoint type: query parameter filters on GET list endpoints, and request body filters on POST search and reporting endpoints.

POST body filters

POST-based search and reporting endpoints accept an optional query.filters array in the request body. Each entry targets a specific dimension and value to narrow the result set.

Filter object fields

Common resource_type values

Multiple filters in the array are combined with AND logic — each additional filter further narrows the result set.
POST body filters (query.filters) are a separate mechanism from query-parameter filters (?filter=...). POST endpoints do not accept the ?filter= query parameter, and GET endpoints do not accept a request body.

Query-parameter filters (GET endpoints)

Syntax

Operators

Since operators are not URL-safe, use the encoded values unless your HTTP client handles URL encoding automatically.

Example

Filter affiliates to only return those with an active account status:
Multiple filters can be combined by repeating the filter parameter.