Prospect Search API - Work Email and Mobile Phone Finder

Search a B2B prospect database by job title, seniority, department, location, headcount, revenue, technologies and funding stage, count the segment for free, then reveal verified work email addresses and mobile phone numbers for the people in it. One flat row per person or company.

What this actor does

• Counts a segment before you pay to reveal it. The search mode returns how many people match your filters plus a sample of who they are, and spends no provider credits. Every preview row carries the true segment size, so you can tighten filters until the number is right and only then reveal.
• Reveals in bulk or one at a time. List mode hands the whole filter set to the provider, waits for it to finish, and writes out every revealed contact with email and phone. Individual reveal works from profile URLs, known email addresses, or names paired with an employer.
• Waits properly for asynchronous jobs. Revealing contacts is a job, not a request. The actor polls with a widening interval up to a timeout you set, reports the state as it goes, and only writes rows once the provider says the job finished.
• Filters on the things that predict a reply. Job change inside the last 30 to 90 days, headcount growth band, department headcount written as sales:10-50, technologies the company runs, technologies it does not, funding stage and revenue band.
• Separates verified addresses from risky ones. A finished list can be read as everything it resolved, only the addresses that passed verification, or only the ones that failed, so a send list and a review list come out of the same run.
• Understands include and exclude on every text filter. Titles, companies, industries, technologies and description keywords all take an exclude list, which is how you keep your own company and your existing customers out of a segment.
• Reads messy input. Pasted profile URLs lose their tracking parameters, pasted company URLs reduce to the bare hostname, and an email address reduces to its domain.
• Never charges for a miss. Only rows carrying a resolved person or company are billed.

Input

Field	What it does
mode	Prospect search, prospect list, individual reveal, company search, company enrichment or credits.
jobTitles, jobTitlesExcluded	Match or rule out title text.
jobTitleLevels	Seniority bands, from CXO to entry level.
jobRoles, jobSubRoles	Department and narrower function.
locations, locationsExcluded	Person location, as city, state:, country:, continent: or group:.
companies, companiesExcluded, pastCompanies	Current and former employers.
companyLocations	Where the company sits, written the same way as person locations.
companyIndustries, companySizes, revenue, companyTypes	Firmographics.
technologies, technologiesExcluded	Technographic filters.
companyAnnualGrowth, departmentSizes, fundingStages	Growth and funding signals.
lastRoleChange, lastCompanyChange	Job change recency windows.
profileUrls, emails, fullNames	What to reveal, for individual reveal.
domains, companyNames, companySlugs	Company identifiers for enrichment.
enrichmentLevel	None, partial, phone or full waterfall.
acceptWorkEmail, acceptPersonalEmail, acceptGenericEmail	Which address types to accept.
listSegment	Everything, verified only, or risky only.
skipDuplicates	Skip people earlier lists already revealed.
jobTimeoutSeconds	How long to wait for a reveal job.
requestsPerMinute	Pace the run under your plan's rate limit.
skipNotFound	Leave unresolved inputs out of the dataset.
maxResults	Hard cap on rows, and therefore on spend and run time.
apiKey	Your own API key. Stored as a secret.

Example output

{
  "found": true,
  "mode": "prospectList",
  "query": "Heads of sales, US SaaS",
  "segment": "valid",
  "fullName": "Jane Doe",
  "firstName": "Jane",
  "lastName": "Doe",
  "jobTitle": "Head of Sales",
  "email": "jane.doe@example.com",
  "emailType": "work",
  "emailStatus": "valid",
  "linkedinUrl": "https://www.linkedin.com/in/example",
  "location": "San Francisco, California, United States",
  "company": "Example Inc",
  "companyDomain": "example.com",
  "companyIndustry": "Computer Software",
  "companySize": "201-500",
  "companyFounded": 2014,
  "companyRevenue": "$25M-$50M",
  "companyType": "private",
  "companyLastFundingRound": "series_b",
  "companyLastFundingAmount": 32000000,
  "companyLocation": "San Francisco, California, United States",
  "error": null,
  "raw": { }
}

Frequently asked questions

What is a prospect search API?

A prospect search API is a query interface over a database of working professionals and the companies they work for. Instead of scraping profiles one by one, you describe the people you want with filters such as job title, seniority, department, location, company headcount, revenue band, technologies the company runs and how recently the person changed jobs, and the API returns everyone who matches. This actor exposes those filters as actor input and writes the matches to a dataset, one row per person, with the option to reveal each person's work email address and mobile number.

How do I find someone's work email address and phone number?

Use individual reveal when you have specific people, and prospect list when you have a filter set. Individual reveal accepts a profile URL, a known email address, or a full name together with a company domain or company name, and returns the work address, the mobile number and the verification status of the address. Prospect list does the same thing for a whole segment at once: it hands your filters to the provider, waits for the reveal job to finish, and writes out every contact it resolved. Set enrichmentLevel to phone or full when the mobile number matters, since the cheaper levels return the email only.

How do I avoid wasting credits on a bad segment?

Run prospectSearch first. It reports how many people match your filters and returns a free sample of up to thirty of them without spending any provider credits, and each row carries the true segment size. Adjust the filters until the count is the size you intended, then switch the same input to prospectList to reveal it. This matters because a filter that is one degree too broad, such as a title match without a seniority band, can multiply a segment tenfold, and you only find that out after paying if you reveal first.

What is the difference between the valid and risky segments?

A finished list separates addresses that passed verification from those that did not. valid returns only the addresses confirmed deliverable, which is what you send to. risky returns the ones that failed or could not be confirmed, usually catch-all domains and addresses whose mail server would not answer. people returns everything the list resolved. Sending to the risky segment is what damages a sending domain's reputation, so it is worth pulling it separately and either verifying it another way or leaving it alone.

Can it filter on the technologies a company uses?

Yes, in both directions. technologies keeps only companies running what you name, and technologiesExcluded rules out companies running something else, which is the usual way to skip accounts that already bought a competitor. Technographic filters combine with the firmographic ones, so a segment such as "companies of 201 to 500 people, running a named CRM, that grew headcount more than 20 percent last year, whose head of sales started in the last 90 days" is a single filter set rather than four separate lists you have to intersect yourself.

Does this work for account based prospecting?

Yes. companySearch finds the accounts matching company filters and returns firmographics, funding and profile identifiers for each, and companyEnrich takes domains, company names or profile slugs you already have and appends industry, headcount, revenue band, funding history, location and social profiles. A common two step run is to search for accounts, take the domains out of the dataset, and feed them back in as the companies filter on a people search so every person you reveal belongs to an account you already qualified.

Do I need my own API key?

Yes. This actor is bring your own key: it calls the prospecting API with credentials from your own account, so your plan governs your credits, your rate limit and your data rights. Put the key in the apiKey input, where it is stored as a secret, or supply it as the DATA_API_KEY environment secret. The actor's own charge is separate and is per row resolved, and rows that resolved to nothing are never charged for.

Keyword map

Prospect search API, B2B contact database API, work email finder API, mobile phone number finder, lead list building API, sales prospecting API, job change data, technographic filters, firmographic search, account based prospecting, email verification status, contact enrichment API.