What it does
Lusha Prospect finds people or companies you don’t already have by filtering Lusha’s database — by department, seniority, location, company size, revenue, industry, technologies, and intent. It returns cheap, non-PII previews (name, title, company, location) plus each match’sid and a canReveal list showing which data points exist and what they cost. Hand those ids to Lusha Enrich to reveal contact details only for the matches worth contacting.
Requires Lusha Integration: Set up the Lusha integration before agents can use this tool.
Key features
- Filter-based discovery over Lusha’s full B2B database (top of funnel — find the names)
- Person filters: department, seniority, country/location, required data points
- Company filters: size, revenue, location, industry, NAICS/SIC, technologies, intent topics
- Returns non-PII previews — no reveal credits spent on discovery
- Paginate up to 50,000 results per query
- Each match includes an
idready to pass to Lusha Enrich
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
entity_type | string | No | contact (default) to return people, or company to return companies |
contact_filters | object | No* | Person filters: departments, seniority (ids: 10=founder, 9=c-suite, 8=vp, 7=partner, 6=director, 5=manager, 4=senior, 3=entry, 2=intern, 1=other), existingDataPoints, countries, locations |
company_filters | object | No* | Company filters: names, domains, sizes ([{min,max}]), revenues, locations, naics, sics, industriesLabels, technologies, intentTopics |
page | number | No | Zero-based page index (default 0) |
size | number | No | Results per page, 10–50 (default 25) |
contact_filters / company_filters is required. A contact search can filter on company attributes too — pass both.
Common use cases
Find decision-makers at target-sized companies
Build a target-account list
Page through a large result set
page until you’ve collected enough matches.
What you get back
results[]— each preview includesid, name,jobTitle,company,location,has(available fields), andcanReveal([{ field, credits }])total_matches— total number of records matching the filterspage/size— the page returnedrate_limits— remaining requests for the minute/hour/day window
Best practices
- Prospect first, enrich second — discovery is cheap; only spend reveal credits on the subset worth contacting
- Start broad, then narrow — overly specific filters can return zero matches
- Use
canRevealto see whether a match even has an email/phone before enriching - Page deliberately — each page is a request that counts against rate limits
Troubleshooting
“Provide at least one of contact_filters / company_filters”- Pass a non-empty filter object — see the keys in the Parameters table
- Loosen filters; combining many narrow constraints can eliminate all matches
- Slow down or wait for the window to reset — limits vary by plan
Related tools
- Lusha Enrich — reveal emails, phones, and firmographics for the ids returned here
