Skip to main content
This guide shows you how to scrape Google data at scale using the asynchronous /trigger endpoint. Use this when you have more than 20 inputs, need discovery by keyword, location or input filters, or want delivery to a webhook or S3.
Not sure whether to use sync or async? Read Understanding sync vs. async requests.

Prerequisites

Step 1: Trigger the collection

Send a POST request to the /trigger endpoint with your input array. This example collects five Google Maps places in a single batch:
You should see a 200 response with a snapshot_id:
Save this ID. You need it to check progress and download results.

Discovery with async

Discovery is the primary reason to use async. Most Google discovery modes can return large result sets, and some require structured inputs that aren’t URLs. Discover Google Maps places by location:
Discover Google Shopping products by keyword:
Discover Google Flights by input filters:
Discover Google Hotels by search:

Step 2: Monitor progress

Poll the snapshot status until it shows ready. This takes 30 seconds to several minutes depending on input count and whether discovery is involved.
Status values:

Step 3: Download results

Once the status is ready, download the scraped data:
You’ve successfully triggered, monitored and downloaded a batch Google scraping job. See the Download Snapshot API reference for format options and part-by-part download flow.

Skip polling with webhooks

If you don’t want to poll for status, add an endpoint parameter to receive results automatically:
See Webhook delivery for the full setup.

Limits and constraints

Troubleshooting

You’ve exceeded the concurrent request limit. Reduce the number of parallel requests or combine inputs into fewer, larger batches. Each batch can include up to 1 GB of input data.
Check that all input URLs are valid and correctly formatted for the target Google product. Review the error details in the snapshot response or in the Logs tab of your Bright Data dashboard.
Individual inputs can fail while the overall job succeeds. Check the snapshot response for any errors field and retry failed inputs in a separate request.
Verify your discovery parameters. Location-based Maps discovery needs valid lat/long and a realistic zoom level (12 to 16). Flights discovery needs IATA codes and future dates. Hotels discovery needs a valid destination string.

Next steps

Webhook delivery

Push results to your HTTP endpoint automatically.

API reference

Full endpoint specs, parameters and response schemas.