Skip to content

Yellow Pages Business Listings Scraper API

Yellow Pages listing pages hold a lot of structured business detail — names, phone numbers, addresses, categories, websites, hours, ratings and review counts.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a hosted scraping API turns a Yellow Pages URL into that data in a single call, what each request parameter does, how credits are consumed, and where the legal and terms-of-service boundary sits before you scale up.

What a Yellow Pages request returns

A single call against a Yellow Pages business-listing page can return the business name, phone number, address, category, website URL, operating hours, ratings, review count and years in business. You choose the output shape: structured JSON (via extraction rules) or rendered HTML for your own parsing. The API handles JavaScript rendering, proxy rotation and anti-bot measures on its side, so you do not manage a headless browser fleet yourself.

Three common jobs this data supports

Most Yellow Pages scraping falls into one of three jobs. First, gathering phone numbers, contact emails and addresses for lead generation or B2B outreach. Second, mapping listings to their primary category and related-category tags for directory or market-research work. Third, pulling website URLs, operating hours and years-in-business per listing for B2B discovery and lead enrichment. Decide which job you are doing first, because it determines which fields you actually need to extract and therefore how much of each page you must parse.

Field and control map: which parameter produces which result

Use this map to match the data you want with the request setting that gets it. It is a planning aid, not a guarantee that every field appears on every listing — some businesses simply do not publish hours, a website or a rating.

  • Business name, phone, address, category, website, hours, ratings, review count — parse from the rendered page; request structured JSON with extract_rules (CSS/XPath selectors) or ai_extract_rules (natural-language spec).
  • JavaScript-dependent content — enable render_js so client-rendered listing blocks appear before extraction.
  • Aggressive blocking or CAPTCHA — enable stealth_proxy on the request.
  • Geo-targeted results — set country_code to route the request through the desired country.
  • Full-page visual record — use the screenshot capability to capture the listing page as an image.
  • LLM-ready text — request the page as clean Markdown to feed a model for enrichment or research.

If a field is missing from the JSON, check first whether the listing actually shows it on the public page before changing selectors.

How credits are consumed

Requests start at 1 credit each. Enabling JavaScript rendering costs 5 API credits per successful request. Premium proxies cost 10 or 25 API credits per successful request, depending on whether JS rendering is disabled or enabled. API credits are valid for one month and do not roll over. That means a single request with both JS rendering and premium proxies can cost 25 credits, so a plan's headline credit count translates into far fewer Yellow Pages pages than the raw number suggests. Estimate your monthly page volume against the per-request cost before choosing a plan tier.

From account to structured data

The workflow has four steps. Create an account to get an API key and free test credits. Install a client SDK in your language of choice (Python, Node, Go, PHP, Ruby) or call the API directly. Send the Yellow Pages URL via GET or POST; the service renders the page, handles anti-bot measures and returns rendered HTML or structured JSON. Then add advanced parameters as needed — render_js, stealth_proxy, country_code, ai_extract_rules — when the basic call is not enough. You can test a request in the dashboard request builder before dropping the generated snippet into your codebase.

Blocked request vs. empty data: tell them apart

When a Yellow Pages run returns less than you expect, the cause is usually one of two different problems, and they need different fixes.

  • Blocked request — you get an error status, a CAPTCHA page or a challenge screen instead of listing content. Fix: enable stealth_proxy, confirm render_js is on, and check that your proxy country matches the listing region.
  • Empty or partial data — the page loads but your JSON is missing fields. Fix: verify the field is actually present on the public listing, then adjust your extract_rules selectors or refine the ai_extract_rules spec. A business with no published website or hours will legitimately return nothing for those fields.

Checking which layer failed before changing parameters saves credits and debugging time.

Running without writing scraper code

You do not need to write a scraper from scratch. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. For workflow automation, the API can be driven from n8n so lead-collection jobs run without scraper code.

Standard and enterprise plan reference
PlanPrice / monthAPI creditsConcurrent requestsPriority email supportDedicated account 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 are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included on every listed plan. Credit validity and per-request costs are described in the credits section above. Treat these figures as a dated reference and confirm current pricing before purchasing.

Frequently asked questions

Do I need a Yellow Pages account to use this API?

No external Yellow Pages account is required. You sign up for the scraping API to get a key and free test credits, then send the listing URL and the service handles the rest.

Is scraping Yellow Pages legal?

Pages that are open to the public are generally fair to collect, but check the target site's terms of service before you deploy anything, and stay away from content that sits behind a login.

What data can I extract from Yellow Pages?

Anything that renders on the public page. Use extraction rules with CSS selectors, or AI-driven extraction with a natural-language spec, to get structured JSON back.

How do I start scraping Yellow Pages?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies and returns the data. Free test credits are included.

Will I get blocked when scraping Yellow Pages?

Requests are routed through rotating residential proxies and a real headless browser so they look like normal traffic. If a target gets aggressive, enable stealth_proxy on the request.

Can I scrape Yellow Pages without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL.