Skip to main content
POST
New Lead Finder search
Several filters only accept exact values from a fixed list: industries, technologies, seniority levels, departments, functions, revenue ranges, funding round names and countries. Look them up in Taxonomies. A value that is not in the list silently matches nothing.
exclude is applied after the search runs, so a request built only from exclude values returns nothing. Always pair it with at least one include.

Pagination

limit and offset paginate a single search. offset is zero-based: keep limit constant and step offset by limit on each call. The total number of matching leads is returned as summary.leads_found, so you know how many pages to walk. If you do not need pagination, use max_leads instead and ignore limit and offset.

Authorizations

X-API-Key
string
header
required

Body

application/json

Filters and parameters for lead finding

filters
object
required

At least one filter value must be provided, otherwise the request is rejected with 400.

limit
integer

Number of leads to return for this request, between 1 and 200. Use it together with offset to paginate. Mutually exclusive with max_leads: when limit is set, max_leads is ignored.

Required range: 1 <= x <= 200
Example:

100

offset
integer
default:0

Zero-based number of leads to skip before returning matches. Only taken into account when limit is set.

To walk through results, keep limit constant and increase offset by limit on each call: 0, then 100, then 200, and so on. The total number of matching leads is returned as summary.leads_found.

Required range: x >= 0
Example:

100

max_leads
integer
default:100

Number of leads to return when you do not paginate. Between 1 and 200, defaults to 100. Ignored when limit is set.

Required range: 1 <= x <= 200
Example:

50

webhook
string<uri> | null

URL that receives the results as soon as the search is done, removing the need to poll. See Webhooks.

Example:

"https://example.com/bettercontact/leads"

enrich_email_address
boolean
default:false

When true, every lead found is also run through the waterfall email enrichment before the results are returned. This consumes enrichment credits on top of the search, and the request stays in processing until enrichment is done.

enrich_phone_number
boolean
default:false

When true, every lead found is also run through the waterfall mobile phone enrichment before the results are returned. This consumes enrichment credits on top of the search. Requires the phone add-on on your plan.

Response

Lead Finder request accepted. Poll GET /lead_finder/async/{request_id} or wait for the webhook.

success
boolean
Example:

true

message
string
Example:

"Lead finder request accepted."

request_id
string
Example:

"bc39ffbfc24cf043b748"