Count profiles matching custom filters

post

https://api.pearch.ai/v2/search/count

Return an estimated count of profiles that match the provided custom_filters.

This endpoint does not run the full search pipeline (no LLM query interpretation). It is intended for quickly checking how broad or narrow a set of filters is before running /v2/search.

The request must include custom_filters with at least one non-empty constraint (for example locations, titles, companies, industries, follower count ranges, etc.).

Expect slower response for expected large counts. E.g. for title="manager" from "US" you should expect slower response and approximate=true in the response. For title="meteorologist" from "tokio" expect faster response and approximate=false in the response.

Cost: 2 credits per call

Rate limit: 60 requests per user per 60 seconds. This endpoint shares the same rate limit as actual /v2/search and /v2/search/submit executions. When the rate limit is exceeded, the API returns HTTP 429 with details about the triggered window, current value, and limit.

Check out official Python client

Body Params

custom_filters

object

required

Custom filters in JSON format for advanced filtering. Leave empty to use default filtering logic.
Format: {"filter_name1": ["value1", "value2"], "filter_name2": ["value3", "value4"], ...}.

Filtering logic: Conditions between different keys are joined with "AND", so all conditions must pass. Within each condition, we always use "OR". For example, {"titles": ["swe", "mle"]} means the profile must have either "swe" OR "mle" as a title. If you specify multiple keys like {"titles": ["swe", "mle"], "locations": ["San Francisco"]}, the profile must match at least one title (swe OR mle) AND be in San Francisco.

Use any string values as is. Pearch.ai internally correctly matches them to profile data. E.g. you may pass {"industries": "health"} to filter for profiles in health industry, this will be correctly mapped to pearch.ai internal healthcare industry.
If you want to force no filtering at all (custom_filters or default filters), pass empty object "custom_filters": {}. This will speed up search, increase recall at some relevancy cost.

Responses

400

Invalid parameter values. JSON body contains the error message.

401

Invalid API key

429

Rate limit exceeded. JSON body contains the triggered window, current value, and limit.

200Count computed successfully