Google Scraper API

Send a Google URL or a keyword, get structured JSON back. The Bright Data Google Scraper API covers Maps, Shopping, Search results, AI Mode Search, Flights and Hotels with consistent request and response shapes.

New to Bright Data? Create a free account and get 5,000 free credits every month, no credit card required. That’s up to 5,000 Google records to start scraping. See the free tier.

How it works

You send one or more Google URLs, keywords or structured inputs to the Bright Data Google Scraper API. Bright Data handles proxies, CAPTCHAs and parsing, then returns clean JSON.

Your app  -->  Bright Data API  -->  Structured JSON
           POST /datasets/v3/scrape
           Authorization: Bearer YOUR_API_KEY

All requests use a dataset_id to specify the Google product and return results in JSON, NDJSON, JSON Lines or CSV.

What the response looks like

A single Google Maps place record returned by the Bright Data Google Scraper API on September 6, 2026, trimmed to the fields shown. Run the request yourself in the quickstart.

{
  "place_id": "ChIJS5WVcqWh9YgRHU08rJqLNsQ",
  "name": "The***s",
  "address": "5155 Peachtree Pkwy NW, Peachtree Corners, GA 30092, United States",
  "category": "Shopping mall",
  "rating": 4.6,
  "reviews_count": 5066,
  "url": "https://www.google.com/maps/place/The+Forum+Peachtree+Corners/@33.9808771,-84.2175823,17z/data=!3m1!4b1!4m6!3m5!1s0x88f5a1a57295954b:0xc4368b9aac3c4d1d!8m2!3...",
  "country": "United States",
  "description": "Outdoor mall with a European feel & a collection of upscale chains & boutiques, plus restaurants.",
  "main_image": "https://lh3.googleusercontent.com/gps-cs-s/AHRPTWmZ8YyHocxqtXw40FHlo2WbKu1zLCxcFQrAWkwM9zj_O76dd_9Mpl-H9rjqS7GjsehkGXvpMA4xDse4qi1ysYEJTzwMpwLOqB3BGwkGap8c1-..."
}

Supported data types

Google Maps

Places, reviews, ratings, photos and community stats. Collect by URL or discover by CID, place ID or geographic location.

Google Maps Reviews

Full review text, ratings and reviewer metadata, filtered by a configurable lookback window.

Google Shopping

Product listings, pricing, merchants and specifications. Collect by URL or discover by keyword.

Google Shopping Search US

US-focused product search results with expanded merchant and pricing coverage.

Google SERP 100 Results

Up to 100 organic results per query with language, device and geographic targeting.

Google AI Mode Search

Answers and citations from Google’s AI-powered search experience.

Google Flights

Flight options, pricing and itineraries. Collect by URL or discover by route and dates.

Google Hotels

Hotel rates, availability and amenities. Collect by URL, filter URL or search parameters.

Which dataset IDs to use

Each Google product uses its own dataset_id. Pass the ID as a query parameter on every request.

Product	Dataset ID
Google Maps full info	`gd_m8ebnr0q2qlklc02fz`
Google Maps Reviews	`gd_luzfs1dn2oa0teb81`
Google Shopping	`gd_ltppk50q18kdw67omz`
Google Shopping products search US	`gd_m31f2k0d2m1bah4f3b`
Google SERP 100 Results	`gd_mfz5x93lmsjjjylob`
Google AI Mode Search	`gd_mcswdt6z2elth3zqr2`
Google Flights	`gd_mhng7wen1rw0a3gvpf`
Google Hotels	`gd_mg3gjfmg12tc2n5d4d`

Request methods

The Bright Data Scraper API supports two request methods. Choose based on your volume and latency needs.

Method	Endpoint	Best for
Synchronous	`/scrape`	Real-time lookups, up to 20 URLs
Asynchronous	`/trigger`	Batch jobs, 20 or more URLs, production pipelines

Learn more in Understanding sync vs. async requests. Both endpoints accept the inputs as a bare JSON array, which is what every example on this page uses, or as an object with an input array. Use the object form when you also send custom_output_fields or limit_per_input on either endpoint, or a deliver block on /trigger. See Request body.

Capabilities and limits

Capability	Detail
Output formats	JSON, NDJSON, CSV
Max URLs per sync request	20
Max URLs per async request	Unlimited, up to 1 GB of input per job
Data freshness	Real-time (scraped on demand)
Delivery options	API download, webhook, Amazon S3, Snowflake, Azure, GCS (all destinations)
Pricing	Pay per successful record (see pricing)

Common questions

Is the data scraped in real time?

Yes. Each request triggers a live scrape against Google. There is no cached or stale data. Processing time varies with target-site conditions and scraper workload. The Bright Data Google Scraper API does not publish a fixed response time. A synchronous request waits up to 1 minute, then returns HTTP 202 with a snapshot_id and continues asynchronously. Discovery requests always run asynchronously and take longer depending on result volume.

Why do response times change over time?

Google changes how its pages are served, and the Bright Data Google Scraper API collectors are updated to match. A collector update can change how long a scrape takes even when the success rate stays the same. For production workloads, build against the async workflow or webhook delivery so a longer run does not break the integration.

What is the difference between Collect and Discover?

Collect by URL scrapes a specific Google page you provide, such as a single Maps place, a Shopping product or a SERP URL. Discover finds Google records matching search criteria such as a keyword, a CID or a geographic area, then scrapes the results. Discovery is most useful via async requests when you don’t know the exact URLs up front.

Can I target a specific country or language?

Yes. Most endpoints accept a country parameter (ISO 3166-1 alpha-2 code), and the SERP 100 endpoint also accepts language and uule for geographic targeting. See each endpoint’s reference page for the full parameter list.

How is this different from scraping using proxies or Web Unlocker API?

When scraping using proxies or Web Unlocker API, you still need to write and maintain your own parsing logic and update it whenever the target site changes its page structure. The Bright Data Scraper API handles the entire stack: proxy rotation, anti-bot bypassing and parsing. You send a URL or keyword and get clean, structured JSON back, with no scraping infrastructure or parser maintenance on your end.

Next steps

Quickstart

Scrape your first Google Maps place in 5 minutes.

Endpoints

One request per endpoint, each with a captured response.

API reference

Endpoint specs, parameters and response schemas.

Get started

Data extraction

Web access

AI training data

Proxy networks

How it works

What the response looks like

Supported data types

Google Maps

Google Maps Reviews

Google Shopping

Google Shopping Search US

Google SERP 100 Results

Google AI Mode Search

Google Flights

Google Hotels

Which dataset IDs to use

Request methods

Capabilities and limits

Common questions

Is the data scraped in real time?

Why do response times change over time?

What is the difference between Collect and Discover?

Can I target a specific country or language?

How is this different from scraping using proxies or Web Unlocker API?

Next steps

Quickstart

Endpoints

API reference

​How it works

​What the response looks like

​Supported data types

Google Maps

Google Maps Reviews

Google Shopping

Google Shopping Search US

Google SERP 100 Results

Google AI Mode Search

Google Flights

Google Hotels

​Which dataset IDs to use

​Request methods

​Capabilities and limits

​Common questions

​Is the data scraped in real time?

​Why do response times change over time?

​What is the difference between Collect and Discover?

​Can I target a specific country or language?

​How is this different from scraping using proxies or Web Unlocker API?

​Next steps

Quickstart

Endpoints

API reference

How it works

What the response looks like

Supported data types

Which dataset IDs to use

Request methods

Capabilities and limits

Common questions

Is the data scraped in real time?

Why do response times change over time?

What is the difference between Collect and Discover?

Can I target a specific country or language?

How is this different from scraping using proxies or Web Unlocker API?

Next steps