Skip to main content

Overview

The Get Filters List API returns every filter accepted by the List Generation API, along with the shape each filter’s value should take, a description of what it matches, and — for filters backed by a fixed set of values — a dropdown_type you can use to look up the allowed values from the Get Filter Options API. Use this endpoint first when building a filter-driven UI or an LLM-based query builder: it tells you which filters exist, how to populate each one, and which filters must be applied together against the same underlying record (see same_element_group below). This is a free endpoint so it does not consume API credits. Endpoint
This endpoint takes no parameters.

Authentication

All requests must include an API key in the x-api-key HTTP header.
Never expose your API key in client-side code, browser requests, or public repositories. A missing or invalid key returns 401 Unauthorized.

Request

Example request:

Response

Filter object fields

dropdown_type is only present on filters backed by a fixed set of values. Filters without it — free-text fields, booleans, numbers, and date ranges — take their value directly with no lookup step.

Understanding same_element_group

Some filters target fields inside a nested array on the company record — for example, a company can have multiple offices, multiple funding rounds, or multiple partnerships. When two or more filters share the same same_element_group, they are constrained to match the same element of that array, not just any element independently. For example, location.offices.city and location.offices.country both carry same_element_group: "location.offices". Filtering on both together means the same office must be in that city and that country — not a company that merely has an office in the city and, separately, an office in the country.

Response envelope

This endpoint does not return a credits_consumed field since it is free and always returns the full, unfiltered set of 41 filters.