ZoomInfo Company & Contacts Scraper

Turn public ZoomInfo company profile pages into rich, structured JSON — company firmographics PLUS the people / leads ZoomInfo surfaces on those pages. Paste one or more company profile URLs and get back, in a single dataset:

1. One rich company record per URL — firmographics enriched with nested arrays: executives, recently-hired people, competitors, technologies, scoops, news, funding rounds, acquisitions, department headcounts, and buyer-intent topics.
2. One flat lead record per person found on the company page (executives + recently-hired) — name, title, department, LinkedIn URL, location, and contact data (email pattern, masked current email/phone, full historical emails).

This actor scrapes the public, logged-out ZoomInfo company pages (/c/<slug>/<id>) and person pages (/p/<slug>/<id>). It does not log in and does not use ZoomInfo's paid API. It returns exactly what ZoomInfo renders to logged-out visitors — current emails/phones are returned masked (as ZoomInfo masks them, e.g. h***@zoominfo.com), while the company email pattern is derived from the public historical addresses ZoomInfo shows in full.

⚖️ Legal & ToS notice — read before you run

This tool collects the publicly visible, logged-out information ZoomInfo exposes (including the public people roster on company pages). You are responsible for your own use of the output. ZoomInfo's Terms of Service and applicable data-protection laws (GDPR / CCPA / etc.) govern what you may collect and how you may use it — especially person-level data. Scrape responsibly, respect rate limits, and ensure you have a lawful basis for processing any personal data in the output. If you need verified / unmasked contact data, use ZoomInfo's official paid API.

Output — record types

Every dataset item carries a record_type field: "company" or "person". The Companies and Contacts / Leads dataset views split them for you.

Company record (record_type: "company")

Field	Example
company_name / short_name / also_known_as	ZoomInfo Technologies LLC / aliases list
website / logo	www.zoominfo.com
hq_location + hq_street/hq_city/hq_state/hq_country/hq_zip	structured address
industry	Customer Engagement Platforms, Software
revenue_band / revenue_usd_thousands	$1.3 Billion / 1254000
employee_band / employee_count	1K - 5K / 3180
founded_year	2000
naics / sic	54,541 / 73,737
is_public / stock_ticker	Public / NASDAQ: GTM
phone / fax	(866) 904-9666 / (617) 507-8187
linkedin_url / twitter_url / facebook_url / instagram_url	company socials
total_funding	2382555
description / summary	public text
employees_likely_to_engage	engagement counter
executives[]	{person_id, full_name, first_name, last_name, title, profile_url, org_chart_tier, likely_to_engage_email/phone}
recently_hired[]	{person_id, full_name, title, profile_url, job_start_date, likely_to_engage_*}
competitors[]	{company_id, name, website, revenue, employee_count, founded_year, is_public, ceo_name, ceo_profile_url}
technologies[]	{name, vendor, relationship: used|owned, market_share?, companies_using?}
scoops[]	{description, date, types[], topics[], link} (open roles, leadership moves, signals)
news[]	{title, url, date, domain, snippet}
fundings[]	{date, amount, amount_value, round, investors[]}
acquisitions[]	{company_id, name, date}
departments[]	{level, count} (C-Level / VP / Director / Manager / …)
intents[]	{topic, signal_score, signals_number} (buyer-intent)
executive_count / recently_hired_count / contacts_scraped	counts
top_executives_url / profile_url / scraped_at	provenance

Person / lead record (record_type: "person")

Emitted when Include contacts is on (default). One row per person fetched from the company page roster.

Field	Example
full_name / first_name / last_name	Henry Schuck
title / job_function / department / management_level	Founder & CEO / Executive / C-Suite / C-Level
linkedin_url	https://www.linkedin.com/in/hschuck
email	masked current email, e.g. h***@zoominfo.com
email_pattern	derived, e.g. {first}.{last}@zoominfo.com
past_emails[]	full historical addresses ZoomInfo exposes publicly
phone / mobile	masked, e.g. (360) ***-****
company_phone	full, (866) 904-9666
city / state / metro_area / country / postal_code / street	person location
education / biography / current_job_duration	profile detail
company_id / company_name / company_website	employer linkage
profile_url / scraped_at	provenance

About emails & phones (important, honest): logged out, ZoomInfo masks the current email and phone (h***@…, (360) ***-****). What it exposes in full is a list of historical addresses (past_emails) — from which this actor derives the company's email_pattern (e.g. {first}.{last}@company.com). That pattern, plus the person's name + LinkedIn, is what makes these usable B2B leads. We only emit a pattern on the person's current employer domain; if we can't confirm it, email_pattern is null rather than a guess on a stale domain.

Input

Field	Description
Company profile URLs	Public profile URLs https://www.zoominfo.com/c/<slug>/<id>.
Include contacts / leads	Default on. Also fetch person pages and emit lead rows.
Max contacts per company	Ceiling on person pages per company (default 25).
Max companies	Safety ceiling on company records.
Proxy exit country	Two-letter exit country (default us).

How to find profile URLs: search the web for site:zoominfo.com/c <company name> — the first result is usually the company's public profile. Copy that URL in.

{
  "companyUrls": [
    "https://www.zoominfo.com/c/zoominfo-technologies-llc/344589814"
  ],
  "includeContacts": true,
  "maxContactsPerCompany": 25,
  "maxItems": 100
}

How it works

ZoomInfo uses enterprise-grade protection. This actor routes every request through a managed proxy fully baked into the actor — you never supply a proxy, API key, or login. All transport cost is included in the per-record price.

Parsing is anchored on the page's structured server-rendered data (the Angular SSR ng-state blob and JSON-LD), not on fragile CSS class names — so it keeps working across ZoomInfo's frequent front-end rebuilds. The first request to a cold domain runs a full unlock cycle (can take 60–120 s); requests retry with backoff so the warm cache then serves fast.

Pricing

Pay-per-result with two separate events:

• company-record — charged once per company record delivered.
• contact-record — charged once per person / lead record delivered.

Failed or blocked URLs are skipped and not charged. Turn Include contacts off to get company records only.

Limitations

• Input is profile URLs (the reliable public path). Logged-out company-name search does not return query-specific results without authenticating, which this actor never does.
• Revenue / employee figures are the bands ZoomInfo publishes (e.g. 1K - 5K).
• Current emails and direct phones are masked by ZoomInfo logged out; the actor returns them as-is (masked) plus the derived email_pattern and full past_emails. It does not unmask paywalled data.
• The contact roster is the set of people ZoomInfo surfaces on the public company page (executives + recently-hired), not ZoomInfo's full employee database.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• 2GIS Places Scraper
• B2B Leads List Builder
• Company Lookup Scraper
• Email Finder
• Epa Data Scraper
• Firmy Cz Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.