/trigger endpoint. Use this when you have more than 20 URLs, need discovery, or want delivery to a webhook or S3.
Prerequisites
- A Bright Data account with an active API token
- Familiarity with the synchronous request flow
Step 1: Trigger the collection
Send aPOST request to the /trigger endpoint with your input URLs:
200 response with a snapshot_id:
Step 2: Monitor progress
Poll the snapshot status until it showsready. This takes 30 seconds to several minutes depending on the number of URLs.
| 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 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 LinkedIn URLs. Review the error details in the snapshot response or in the Logs tab of your Bright Data dashboard.
Results are incomplete or missing some URLs?
Results are incomplete or missing some URLs?
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.Next steps
Set up webhooks
Receive results without polling.
Deliver to S3
Send results directly to your S3 bucket.