Skip to content

Scrape ZoomInfo Business Listings and Contact Data

ZoomInfo pages mix server-rendered markup with client-side content, which makes a plain HTTP fetch unreliable.

OUTPUT FORMATSHTMLJSONMarkdown

A hosted scraping API handles the browser, proxy rotation, and bot-detection layer so your code only has to send a URL and read the response. This page explains what the API returns, which request options change the output, and how credits and concurrency work so you can size a job before you run it.

What the API does with a ZoomInfo URL

You send one HTTP request containing your API key and a ZoomInfo URL. The service rotates residential proxies, spoofs browser fingerprints, and renders JavaScript in a headless browser. The response is post-render HTML, or parsed JSON when extraction rules are supplied. Two output shapes are available: raw HTML for your own parser, and structured JSON via CSS selectors or a natural-language extraction spec.

The three workflows this data usually supports are contact extraction for lead scoring, company financial aggregation for market analysis, and job-listing collection for hiring-trend review. Each workflow has different field needs, which is why the extraction step matters more than the fetch step.

Request options and what each one changes

The options below are the ones that materially change the response. Treat them as a field map: pick the option that matches the output you need, not the largest set of options.

  • render_js=true runs the page in a real headless browser, executes the JavaScript server-side, and returns the post-render HTML. Use this when the content you need appears only after scripts run.
  • country_code routes the request through a residential IP in that country. Use this when the page varies by geography.
  • extract_rules maps CSS selectors to field names and returns parsed JSON.
  • ai_extract_rules takes a natural-language spec and returns parsed JSON.
  • stealth_proxy is the higher-cost proxy tier for pages that block standard rotation.
  • premium_proxy is the mid-tier proxy option; its credit cost depends on whether JS rendering is also enabled.

A practical sequence is: start with the default request, add render_js if the target content is missing, add country_code only if geo matters, and add extraction rules once the HTML shape is stable.

Credit costs and a worked example

Requests start at one credit each. Options add to that base. JavaScript rendering costs 5 credits per successful request. Premium proxies cost 10 credits without JS rendering or 25 with it. Stealth proxy costs 75 credits. API credits are valid for one month and do not roll over.

Worked example: a job that needs rendered JavaScript and a stealth proxy costs 75 credits per request in the stealth tier. At 1,000 free signup credits, that is roughly 13 such requests before the free balance is used. A job that only needs JS rendering costs 5 credits per request, so the same 1,000 credits cover about 200 requests. Run this arithmetic against your expected page count before choosing a plan, because the option mix, not the page count alone, drives the bill.

Concurrency limits versus target-side throttling

The API enforces concurrency limits per plan, not per-target rate limits. Concurrency is the number of requests that can be in flight at the same time. If ZoomInfo itself throttles aggressive request patterns, the fix is on your side: space out requests or use multiple sessions. Raising your plan's concurrency will not remove a target-side block, and lowering it will not fix one either. Diagnose which limit you hit before changing plans.

Languages and setup path

SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works as well. Code samples exist for Python, Node.js, Ruby, PHP, Go, and cURL, and the dashboard includes a request builder for testing without writing code. Setup is a four-step path: create an account to get an API key and free credits, install the SDK for your stack, send one HTTP call with the key and a ZoomInfo URL, then add advanced parameters as needed.

Choosing a plan by credit volume and concurrency

Plans differ on three axes that matter for this job: monthly API credits, concurrent requests, and whether priority support, a dedicated account manager, and team management are included. The standard tiers run from a low-volume entry plan up through higher-credit tiers, and the enterprise tiers extend credits and concurrency further. All tiers include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules. The support and team features are the main differentiator at the top end.

Use the credit arithmetic above to estimate monthly volume, then check that the plan's concurrency matches your peak parallel job count. If you need more credits or concurrency than the listed tiers, the sales contact path is the right next step rather than stacking plans.

Data handling and compliance posture

The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and mimic real user browsing behavior. Compliance obligations for the data you collect remain with you as the operator; confirm your own basis for processing contact data before running a job.

Request option map
OptionWhat it changesWhen to use it
render_jsRuns the page in a headless browser and returns post-render HTMLContent appears only after scripts execute
country_codeRoutes through a residential IP in the chosen countryPage content varies by geography
extract_rulesMaps CSS selectors to field names and returns JSONYou know the page structure and want parsed output
ai_extract_rulesTakes a natural-language spec and returns JSONYou want parsed output without writing selectors
premium_proxyMid-tier proxy; 10 credits without JS, 25 with JSStandard rotation is blocked but stealth is not required
stealth_proxyHigher-cost proxy tier; 75 creditsThe target blocks standard and premium rotation

Credit figures are the captured per-request costs; confirm current pricing before committing a budget.

Plan comparison (captured reference)
PlanPrice / monthAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$1975,00025Not includedNot includedNot included
Freelance$49250,00050Not includedNot includedNot included
Startup (Recommended)$991,000,000100Not includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncluded

Prices exclude VAT. Figures are a captured reference and may change; verify current pricing and plan terms before purchase.

Frequently asked questions

How do I handle JavaScript when scraping ZoomInfo?

Set render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I scrape ZoomInfo from a specific country?

Yes. Set country_code on the request to route through a residential IP in that country. This matters when the content you see varies by geography.

What's the rate limit for scraping ZoomInfo?

The API applies concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from ZoomInfo?

You have two routes to parsed output. The selector route uses extract_rules, where each CSS selector is paired with the field name you want it stored under. The descriptive route uses ai_extract_rules, where you describe the fields in plain language instead of writing selectors. Either way, the response arrives as parsed JSON rather than raw markup.

Which programming languages can I use to scrape ZoomInfo?

Any language that can make an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.

How much does it cost to scrape ZoomInfo?

Signup includes 1,000 free credits with no card required. Paid plans start at $19/month for higher volume and concurrency. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.

What is the difference between a concurrency limit and a rate limit?

Concurrency is how many requests can be in flight at once, and it is set by your plan. A rate limit is how often a target site accepts requests. If ZoomInfo throttles you, changing your plan's concurrency will not help; adjust request spacing or session handling instead.