People and company tools

"find fintech companies in London with 50 to 200 staff", "companies that do X", building an account list by firmographics.

• One known company, use leads_get_company (by domain).
• People at companies, use leads_search_people.
• A site's traffic, use seo_get_domain_overview.
• Local shops and services in an area, use maps_search_businesses.

A list. Each row has id, name, domain, website, linkedin_url, industry, employees, headcount_range, headcount_growth[] (months, percent), location, founded_year, company_type, description, keywords[], revenue_min and revenue_max (the estimated annual revenue range, USD), phone. rows_available is the provider's total before the keyword check. A row is kept only when one of the keywords or unlisted industries appears in its name, industry, description or specialties, so a page can return fewer rows than limit; the charge counts the rows fetched.

12 credits per 100 rows asked for (limit), rounded up. Default 12 credits. Cached 30 days.

"tell me about acme.com", sizing a company, the industry, revenue range and headcount growth behind a domain, filling in a search row.

• Search traffic and rankings, use seo_get_domain_overview.
• Who works there, use leads_search_people.
• Email addresses, use leads_get_domain_emails.

One record with id, name, domain, website, linkedin_url, industry, industries[], employees, headcount_range, headcount_growth[] (months, percent), location, founded_year, company_type, description, keywords[], revenue (USD, where disclosed), revenue_min and revenue_max (the estimated range, USD), total_funding, funding_stage, technologies[], phone, ticker. null = the provider does not hold it; total_funding, funding_stage, technologies and ticker are always empty. NoData when the provider does not know the domain.

1 credit. Cached 30 days.

"find heads of marketing at fintech startups", building a target list by role, prospecting by ICP.

• Someone to email at a specific website about a link, use leads_get_domain_emails (keyed by domain).
• One person's full record, use leads_get_person.
• An email for a named person, use leads_get_email.

A list. Each row has id (the LinkedIn profile URL; null when the person has no profile, so look them up by name and domain), first_name, last_name, headline, title, title_start (YYYY-MM, so time in the role), company, company_domain, company_id, company_linkedin_url, company_employees, company_industry, location, linkedin_url. rows_available is the provider's total.

12 credits per 100 rows asked for (limit), rounded up. Default 12 credits. Cached 7 days.

Filling in a search row by id, "who is the head of growth at acme.com", checking a person's current role before outreach.

• The email, use leads_get_email (the paid reveal).
• Many people at once, use leads_search_people.

One record with id, first_name, last_name, headline, title, title_start, seniority, company, company_domain, company_id, company_linkedin_url, company_employees, company_industry, location, linkedin_url, has_email, summary, employment_history[] (company, title, start, end, current; newest first), education[] (school, degree, field, start, end), skills[], languages[]. Dates are YYYY-MM. null or empty = the provider does not hold it; looked up by name and domain, the history is the current role only and education, skills and languages are empty. NoData when nobody matches.

9 credits by id or linkedin_url, 3 by name and domain, nothing on NoData. Cached 30 days.

You have a person and their company and need an address to send to, "get me the email of Jordan Blake at acme.com", after leads_search_people found the person.

• Anyone at a website (no name), use leads_get_domain_emails.
• Checking an address you already hold, use leads_get_email_status.
• The person's role and history, use leads_get_person.

One record with first_name, last_name, domain, email, confidence (0 to 100, null when the source gives none), verification_status (valid | accept_all | invalid | unknown), found_by (the source that hit), position, linkedin_url, twitter, phone, sources[] (url, last_seen_at: where the address was seen). verification_status is the verdict of the source that hit: some sources return only addresses they verified themselves, catch-all domains included, so their hits read valid with null confidence and no sources; only a hit with no verdict is checked by an additional verifier before it is returned. leads_get_email_status asks that verifier separately, which can call the same address accept_all. position, linkedin_url, twitter, phone and sources are null or empty unless the source that hit reports them. NoData when no source finds one; do not retry. meta.providers_tried lists the sources asked, in order; with an id and no name the first is the people source that turns the profile into a name and domain, not a finder that missed. A source that does not answer in time is skipped; when none answers, ProviderUnavailable at no charge.

7 credits on a hit, 31 when certain providers are used, plus 9 for an id given without a name; nothing on NoData. Cached 90 days.

"is jane@acme.com still valid", cleaning a list before a send, checking a shortlist from leads_get_domain_emails.

• Finding an address, use leads_get_email or leads_get_domain_emails.

One record with email, status (valid | invalid | accept_all | unknown; accept_all means the server takes anything, so the address is unproven), result (deliverable | undeliverable | risky | unknown), score (0 to 100), mx_records, mail_provider (who runs the mail servers: google, microsoft, or a filter such as mimecast). disposable, webmail and smtp_check are null: the verifier does not report them, so judge free-mail and throwaway domains by the domain.

1 credit. Cached 30 days.

"find someone to email at these sites about a backlink", "who runs content at example.com", "get contacts for the referring domains of X".

• One named person, use leads_get_email.
• People by title across many companies, use leads_search_people.
• Checking an address works, use leads_get_email_status.
• Choosing which sites to contact, use seo_get_referring_domains, seo_get_backlinks, seo_get_domain_ratings.

A list, highest confidence first. Each row has domain, email, first_name, last_name, position, department, seniority, decision_maker, type (personal | generic), confidence (0 to 100), verification_status, sources[] (url, last_seen_at; empty = inferred from the domain's pattern), linkedin_url, twitter, phone. domains[]: domain, pattern (the address format, for example {first}.{last}), organization, accept_all (true = the server takes any address, so no address there can be proven), webmail, disposable, linked_domains[], rows_available. errors[] lists domains that failed. Addresses come back unverified for the most part; verify the shortlist with leads_get_email_status, not the whole list.

1 credit per domain + 30 per domain that returns addresses, whatever the limit. Default one domain with 30 addresses = 31 credits. Cached 30 days.

"which companies are hiring an SEO manager in London", hiring for a role as a buying signal, "who is hiring people who use HubSpot", what a role pays.

• Every opening at one company, which Google Jobs does not answer (a company's name in the keyword finds jobs that mention it); read its careers page with seo_get_page.
• People who already hold a role, use leads_search_people.

One record with keyword, Each row has rank, job_id, title, company, company_url, location, source (the board or careers site), url (the posting there), salary (as written), contract_type, posted (YYYY-MM-DD, only to the day). No description text. One role on several boards can fill several rows.

1 credit per 20 results. Default 20 = 1 credit. Cached 1 day. Can take up to a minute.