Contact Info Scraper for Business Outreach Data
Public contact pages are a practical source of business names, email addresses, phone numbers, office locations, and team details.
This hosted scraping API lets you request those pages at scale and receive either rendered HTML or parsed JSON, so the output fits the next stage of your pipeline rather than forcing you to manage browsers and proxies yourself.
What you can extract from public contact pages
A contact page or public business directory usually exposes several kinds of information: the organization name, one or more email addresses, phone numbers, office addresses, named team members with titles, and social media handles. The API returns whatever renders on the public page, so the practical limit is the page content itself rather than a fixed field list.
There are three common jobs behind this data collection. The first is gathering structured contact details for a CRM or outreach list. The second is identifying decision-makers by pulling public names, titles, roles, companies, and contact channels from corporate sites. The third is building partner, prospect, or vendor-research lists from public directories. Each job benefits from a consistent output shape, which is why the structured JSON option matters more than raw HTML for repeatable workflows.
How the request flow works
The workflow is deliberately short. Create an account to receive an API key and starting credits. Install one of the published SDKs or use plain cURL. Send a GET request with your API key and the URL of a page that has a public contact section. The service renders JavaScript, rotates residential proxies, and returns rendered HTML ready to parse.
When a page needs more than a basic fetch, advanced parameters are available. render_js enables JavaScript rendering, stealth_proxy helps with CAPTCHA-protected pages, country_code sets geo-targeting, and ai_extract_rules supports natural-language extraction. For selector-based extraction, extract_rules maps CSS selectors to field names. The response can come back as parsed JSON when extraction rules are supplied.
Rendered HTML or structured JSON: a decision checklist
Choose rendered HTML when you need to inspect the page as a browser sees it, when selectors are still being developed, or when a downstream parser already handles HTML. Choose structured JSON when you want field names mapped directly to values and a stable shape for a database or CRM import.
A short checklist helps before you commit to one path:
- Does the target page load contact details through JavaScript? If so, enable rendering.
- Are the fields consistent across pages? If yes, CSS selector extraction rules are usually enough.
- Are field names or page structures inconsistent? Natural-language extraction rules may fit better.
- Do you need a visual record of how the page rendered? A screenshot option is available separately.
- Will the output feed an LLM or a text pipeline? Markdown output is another option.
These choices are not mutually exclusive. You can start with HTML to understand the page, then move to extraction rules once the selectors are stable.
Field and control map
The request surface is small enough to map directly. The URL is the page you want to read. The API key authenticates the request. render_js controls whether JavaScript is executed. stealth_proxy selects the anti-bot path. country_code sets the proxy geography. extract_rules takes CSS selectors mapped to field names. ai_extract_rules takes a natural-language specification. The response is either rendered HTML or parsed JSON, depending on whether extraction rules were supplied.
This map is useful when debugging: if the response is HTML but you expected JSON, check whether extraction rules were included. If fields are missing, check whether the selector matches the rendered DOM rather than the raw source.
A worked cost example
Credit consumption depends on the options enabled per request. The supplied figures are: 5 credits for JavaScript rendering, 25 credits for premium proxy with JavaScript rendering, and 75 credits for stealth proxy. A plain request starts at 1 credit.
Suppose you need to read 1,000 contact pages with JavaScript rendering enabled. At 5 credits per successful request, that is 5,000 credits. If those same pages require the stealth proxy path at 75 credits each, the same 1,000 pages would consume 75,000 credits. The gap is large enough that it is worth testing a sample of pages with the cheapest option that works before scaling up.
API credits are valid for one month and do not roll over. Paid plans start at $19 per month, and a starting allowance of 1,000 free credits is available without a card. Prices are exclusive of VAT.
Three failure modes worth telling apart
A failed extraction is not always the same problem. First, the page may be blocked before rendering: the request never reaches the contact content, and the fix is usually a proxy or anti-bot option rather than a selector change. Second, the page may render but the selector may not match: the HTML is present, but the field comes back empty because the CSS path targets the wrong element or the DOM changed. Third, the page may render and the selector may match, but the value may be absent from the public page itself: the contact detail is simply not published.
Separating these cases prevents wasted tuning. If the HTML response contains the contact block but the JSON field is empty, the problem is in the extraction rules. If the HTML response does not contain the contact block at all, the problem is earlier in the request path.
Languages and setup
Published SDKs cover Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works as well. The setup path is the same across stacks: obtain a key, install the client if you want one, and send a request with the target URL. The documentation includes code samples for these languages, and the knowledge base covers common use cases. A first request can be made in a few minutes once the key is in hand.
Compliance and responsible use
Public-facing pages can usually be read, but the target site's terms of service should be reviewed before deployment, and post-login content should be avoided. The service does not collect or store personal data from scraped sites unless the user explicitly requests it. Data protection obligations still rest with the team running the collection, so retention rules and lawful basis should be settled before a pipeline goes live.
| Plan | Price per month | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
Prices are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every plan listed. This is a captured reference and should be checked against current pricing before purchase.
| Request option | Credits per successful request |
|---|---|
| Plain request | 1 |
| JavaScript rendering | 5 |
| Premium proxy without JavaScript rendering | 10 |
| Premium proxy with JavaScript rendering | 25 |
| Stealth proxy | 75 |
Credit figures follow the request-option contract: a plain request starts at 1 credit, JavaScript rendering costs 5, premium proxies cost 10 without JavaScript rendering or 25 with it, and stealth proxy costs 75. API credits are valid for one month and do not roll over.
Frequently asked questions
Do I need an account to scrape contact info?
Yes, you need an API key. Signing up provides 1,000 free credits without a card, and the key is used to authenticate each request. No separate account on the target site is required.
Is scraping contact info legal?
Public-facing pages can usually be read, but the target site's terms of service should be reviewed before deployment, and post-login content should be avoided. Legal compliance depends on the jurisdiction and the specific use of the data.
What data can I extract from contact info?
The scraper can return any content that appears on the rendered public page. To turn that content into a structured result, supply extract_rules with CSS selectors, or use ai_extract_rules to describe the fields you want in natural language; either route returns parsed JSON. Typical targets include business names, email addresses, phone numbers, office locations, team-member details, and social media handles.
How do I get structured JSON from contact info?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.
Which programming languages can I use to scrape contact info?
Any language that can send an HTTP request. Published SDKs cover Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works as well.
How much does it cost to scrape contact info?
Signing up provides 1,000 free credits without a card. Paid plans start at $19 per month. Credit cost per request depends on the options: 5 credits for JavaScript rendering, 25 for premium proxy with JavaScript rendering, and 75 for stealth proxy. API credits are valid for one month and do not roll over.