/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.
Prerequisites
- A Bright Data account with an active API key
- Familiarity with the synchronous request flow
Step 1: Trigger the collection
Send aPOST request to the /trigger endpoint with your input array. This example collects five Google Maps places in a single batch:
200 response with a snapshot_id:
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:Step 2: Monitor progress
Poll the snapshot status until it showsready. This takes 30 seconds to several minutes depending on input count and whether discovery is involved.
| Status | Meaning |
|---|---|
collecting | Scraping is in progress |
digesting | Data is being processed |
ready | Results are available for download |
failed | The collection encountered an error |
Step 3: Download results
Once the status isready, download the scraped data:
Skip polling with webhooks
If you don’t want to poll for status, add awebhook parameter to receive results automatically:
Limits and constraints
| Constraint | Value |
|---|---|
| Max inputs per async request | 5,000 |
| Max input file size | 1 GB |
| Max concurrent batch requests | 100 |
| Max concurrent single-input requests | 1,500 |
| Webhook delivery size | Up to 1 GB |
| API download size | Up to 5 GB |
Troubleshooting
Getting a 429 Too Many Requests error?
Getting a 429 Too Many Requests error?
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.
Snapshot status shows 'failed'?
Snapshot status shows 'failed'?
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.
Results are incomplete or missing some records?
Results are incomplete or missing some records?
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.Discovery returned zero results?
Discovery returned zero results?
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.