Skip to main content
This reference lists every documented Bright Data Scraper API limit in one table, with what happens when a request reaches each one.

What are the Scraper API limits?

How do I avoid the HTTP 429 limit?

Combine many inputs into one /trigger request instead of starting one job per input. A single job accepts up to 1 GB of input data, so fewer, larger jobs keep you under the 5,000 running jobs limit. When a 429 arrives, stop sending, wait the seconds in the Retry-After header when present, otherwise back off 2, 4, 8, 16 and 32 seconds with jitter, then retry. Stop after a fixed number of retries. The retry code is in Getting a 429 Too Many Requests error?, and every Scraper API error message is listed on Scraper API error codes.

FAQ

How many URLs can I send in one Scraper API request?

Bright Data recommends one input per synchronous /scrape request, because more inputs are less likely to finish within 1 minute. This is a recommendation, not a hard limit. A /scrape request that cannot finish within 1 minute returns HTTP 202 with a snapshot_id and the job continues asynchronously. The asynchronous /trigger endpoint accepts up to 1 GB of input data per job. See How to scrape in bulk with async requests.

Does a sync request fail after 1 minute?

No. A /scrape request that runs past 1 minute returns HTTP 202 with a snapshot_id, and the job keeps running. Poll Monitor progress with the snapshot_id, then fetch the records with Download snapshot.