Phone Number Scraper for Public Listings
A phone number scraper is only useful if the numbers it returns are the ones you actually need, in a shape you can use.
This page explains what an API-driven approach to public phone number collection returns, which request controls change the outcome on JavaScript-heavy or protected pages, and how the plan tiers differ. It is written for developers and data teams evaluating whether to send a URL and receive structured contact data rather than maintain headless browsers and proxy pools themselves.
What the scraper does
You send a target URL that contains publicly visible phone numbers. The service renders the page in a real headless browser, rotates residential proxies, and applies bot-detection handling before returning the response. The result is the page content after rendering, ready to parse or to pass through extraction rules.
The three jobs this pattern usually covers:
- Building outreach lists from public business directories and contact pages.
- Collecting competitor or vendor support-line numbers for service benchmarking.
- Gathering publicly posted feedback or contact channels that inform product decisions.
Each job has a different tolerance for missing fields. A lead list needs the phone number and business name to be present together; a benchmarking job needs the support line plus the page it came from so the comparison stays traceable. Decide which fields are mandatory before you write extraction rules, because a rule that matches nothing returns nothing rather than an error.
Fields you can expect back
On pages that expose contact details, the response can include business name, phone number, address, contact role, and operating hours. These are not guaranteed on every page: a listing that publishes only a name and a number will return only those. Treat the field list as a map of what to look for, not a promise that every URL fills every column.
A practical field map:
- Business name — the entity the number belongs to; use it as the join key when merging pages.
- Phone number — the primary value; normalize formatting after extraction rather than during it.
- Address — useful for deduplication when the same business appears in several directories.
- Contact role — tells you whether the number reaches a general line, sales, or support.
- Operating hours — helps you decide when a number is likely to be answered.
If a field matters to your downstream process, add a presence check before you trust the row. Rows missing a mandatory field should be flagged, not silently dropped, so you can see whether the gap is a page problem or a rule problem.
Request controls and the failure each one addresses
The API accepts a URL plus optional parameters. The useful ones for phone number collection map to specific problems:
- render_js — set this when the number appears only after client-side JavaScript runs. Without it you receive the pre-render HTML, which often has no number in it.
- stealth_proxy — enable when a target responds aggressively to automated traffic. It is the escalation step, not the default.
- country_code — route the request through a specific country when the page localizes content or blocks by region.
- extract_rules — supply CSS selectors when you know the page structure and want structured JSON back.
- ai_extract_rules — describe the fields in natural language when the page structure varies across a directory and fixed selectors would break.
A common mistake is enabling stealth_proxy to fix a missing number that is actually a JavaScript rendering problem. Check whether the number exists in the rendered HTML first; if it does not, the proxy setting will not create it.
Worked example: a directory page with a JavaScript-injected number
Suppose a public business directory shows the company name in the initial HTML but loads the phone number from a script after the page opens. A request without rendering returns the name and an empty contact block. The extraction rule for the phone field matches nothing, and the row looks like a page with no number.
The corrected sequence:
- Send the URL with render_js enabled so the script executes server-side.
- Confirm the number now appears in the returned HTML.
- Add an extract_rules selector for the contact block, or an ai_extract_rules description naming business name and phone number.
- Validate a sample of rows against the live pages before scaling the job.
This distinction matters because the two failure modes look identical in output but have different fixes. A missing number caused by unrendered JavaScript is solved by rendering; a missing number caused by a page that genuinely publishes no number is not solved by any parameter. Log which case you hit so the next run does not repeat the wrong fix.
Getting from signup to a first response
The setup path is short: create an account to receive an API key and starting credits, install a client library for your stack or use cURL, then send a GET request with the target URL. Client libraries are offered for Python, Node, Go, PHP, and Ruby, and the dashboard request builder generates a snippet in those languages or cURL if you prefer not to write the call by hand.
Before you scale, run a small batch across the different page types in your target set — a directory listing, a business contact page, and a support page. The rendering and extraction settings that work for one may not fit the others, and catching that on ten URLs is cheaper than on ten thousand.
Plan tiers and what changes between them
Plans differ on three axes that matter for phone number collection: monthly API credits, concurrent requests, and whether priority support, a dedicated account manager, and team management are included. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included from the entry tier upward.
Credit consumption is not one credit per request in every case. Requests start at 1 credit each; a successful request that enables JavaScript rendering costs 5 API credits; premium proxies cost 10 or 25 API credits depending on whether JS rendering is disabled or enabled. Budget from the controls you actually need rather than from the request count alone.
See the plan comparison table below for the full tier breakdown, including credit allowances and concurrency limits.
Legal and compliance considerations
Public-facing pages can usually be collected, but the target site's terms of service should be reviewed before you deploy, and content behind a login should be left alone. Phone numbers are personal data in many jurisdictions, so how you store and use them matters as much as how you collect them.
The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. That describes the service's handling, not yours: once the data is in your system, your own retention and consent obligations apply. If your use case involves contacting individuals, check the rules for your jurisdiction before building the list.
| Plan | Price | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
All prices are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included on every tier. API credits are valid for one month and don't roll over; requests start at 1 credit each, with JS rendering and premium proxies costing more.
| Request type | Credits per successful request |
|---|---|
| Plain request | 1 |
| JavaScript rendering enabled | 5 |
| Premium proxies, JS rendering disabled | 10 |
| Premium proxies, JS rendering enabled | 25 |
Credit costs apply to successful requests. API credits are valid for one month and don't roll over.
Frequently asked questions
Is scraping phone number data legal?
Public-facing pages can usually be collected, but review the target site's terms of service before deploying and avoid post-login content. Phone numbers are personal data in many jurisdictions, so your own storage and use obligations apply once the data is in your system.
What data can I extract from phone number data?
Whatever the public page actually renders is available to you. Structured JSON comes back by either of two routes: point at the elements with CSS selectors via extract_rules, or state the fields you want in everyday language via ai_extract_rules and let the AI layer find them. Where a page publishes contact details, the response may carry business name, phone number, address, contact role, and operating hours.
How do I start scraping phone number data?
Sign up, take the API key you receive, and send a GET request with the target URL. The page is rendered, proxies are rotated, and the response comes back ready to parse. Starting credits are included so you can test before committing to a plan.
Will I get blocked when scraping phone number data?
Requests rotate residential proxies and use a real headless browser, so they resemble normal traffic. If a target responds aggressively, enable stealth_proxy on the request. Before escalating, confirm the number is not simply missing because JavaScript has not rendered — that is a different fix.
Can I scrape phone number data without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL. You still need to decide which fields you want and how to validate them, but you do not need to write the HTTP call by hand.
How do I handle JavaScript when scraping phone number data?
Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and the post-render HTML is returned. If the number only appears after a click or scroll, a JavaScript scenario can simulate that interaction before extraction.