Return the number of profiles that match a natural-language query, structured search_requirements, or custom_filters.

Queries and search requirements use the same TPSQL parsing and filtering behavior as a superfast search, but the endpoint does not return profiles. Custom-filter-only requests continue to use the optimized custom-filter count path unless stats is true.

Set stats to true to aggregate canonical profile fields from a sample of up to 1,000 matching profiles. Repeated values are counted at most once per profile. The response reports the full matching count separately from the sampled profile count. Profile statistics add 5 credits to the request cost.

The request must include at least one of query, search_requirements, or custom_filters. Filters can be combined with either natural-language input and are ANDed with its TPSQL filters, matching /v2/search behavior. If both query and search_requirements are provided, search_requirements takes precedence.

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 for a custom-filter-only request; 5 credits when query or search_requirements is present, including requests that also contain custom filters; plus 5 credits when stats=true.

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