Skip to main content
Use the asynchronous /trigger endpoint to scrape more than 20 URLs in one job, run discovery collections or deliver results to a webhook or cloud storage. The workflow is the same for every Bright Data scraper: trigger, poll, download. Only the dataset_id changes.
Not sure whether to use sync or async? Read Understanding sync vs. async requests.

Prerequisites

Which dataset ID do I use?

Every scraper has its own dataset_id. The examples on this page use LinkedIn profiles. Substitute the ID for the platform you are scraping. Each scraper exposes several endpoints, for example Amazon has separate IDs for products, reviews and sellers. The full list for each platform is on its introduction page, and every ID is browsable in the Scrapers library.

Step 1: Trigger the collection

Send a POST request to the /trigger endpoint with your input URLs:
You should see a 200 response with a snapshot_id:
Save this ID. You need it to check progress and download results.

Step 2: Monitor progress

Poll the snapshot status until it shows ready. This takes 30 seconds to several minutes depending on the number of URLs.
Status values:

Step 3: Download results

Once the status is ready, download the scraped data:
You have triggered, monitored and downloaded a batch scraping job.

Skip polling with webhooks

If you don’t want to poll for status, add an endpoint parameter to receive results automatically:
See Deliver results to webhooks and cloud storage for the full setup.

Limits and constraints

How to limit records per input

When running a discovery collection, you can cap the number of results returned per input. Set this in the scraper’s configuration in the Control Panel.
Limit per input disabled
With a limit of 10, each input returns at most 10 records.
Limit per input set to 10

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 for the scraper you are calling. A LinkedIn URL sent to the Amazon dataset_id fails. Review the error details in the snapshot response or in the Logs tab of your Bright Data dashboard.
Some URLs may fail individually while the overall job succeeds. Check the snapshot response for any errors field. Retry failed URLs in a separate request.

FAQ

How many URLs can I send in one async request?

Async requests accept up to 1 GB of input data per job, which is tens of thousands of URLs. Use the synchronous endpoint only when you have 20 URLs or fewer and want the results in the same response.

Do I need a different dataset ID for each platform?

Yes. The dataset_id query parameter selects both the platform and the endpoint, for example Amazon products versus Amazon reviews. The table above lists the primary ID per platform, and each platform’s introduction page lists the rest.

How long does a snapshot stay available?

Snapshots are downloadable for 30 days after the job completes. Deliver results to a webhook or cloud storage if you need them retained longer.