Skip to main content
POST
Use this endpoint to query Lusha’s contact database with filters aligned to your Ideal Customer Profile. You get back a list of matching contacts with IDs you then pass to the Enrich Contacts endpoint to retrieve full details. This is step 2 of the three-step prospecting flow.
Prospecting flow

Endpoint

Authentication: API key (ApiKeyAuth)

Request body

object
required
The top-level filter container. At least the filters object is required.
object
Pagination controls.
boolean
When true, includes contacts with incomplete data in results. Partial profiles may lack some contact details but can still be useful prospects.
boolean
Scale plan feature. When true, filters out contacts whose phone numbers are all marked Do Not Call.
  • Contacts with at least one callable phone appear in results.
  • Only callable phones are returned - DNC phones are hidden.
  • Contacts with only DNC phones are excluded entirely.
Returns 403 on unsupported plans.

Example request


Response

200 - Success

string
Unique ID for this search. Pass this value to the Enrich Contacts endpoint as requestId.
number
The page number returned.
number
Number of results on this page.
number
Total number of contacts matching your filters across all pages.
object[]
Array of matching contacts.

Error codes

Authorizations

api_key
string
header
required

Your Lusha API key. You can find this in your Lusha dashboard under API settings.

Include this key in the api_key header for all requests.

Body

application/json
filters
object
required
includePartialContact
boolean
default:true

When set to true, includes contacts with partial information in the search results. Partial contacts may have incomplete data but can still be valuable prospects.

Example:

false

excludeDnc
boolean
default:false

When true, excludes contacts whose phones are all marked Do Not Call (DNC). Contacts with at least one callable phone appear in results; only callable phones are returned (DNC phones are hidden). Contacts with only DNC phones are excluded entirely.

Example:

true

pages
object

Response

Search results with contact IDs

requestId
string

The unique request ID used for subsequent enrichment requests

currentPage
number

The current page of the search results

pageLength
number

The number of results on the page

totalResults
number

The total number of search results

contacts
object[]