cURL
Scraper Studio API
Receive batch data
Use GET /dca/dataset?id=<collection_id> to fetch results of an async Scraper Studio batch job. Returns a status object while running, a JSON array when ready.
GET
cURL
Use
When the collection is ready (HTTP 200):
The exact field set depends on the output schema you defined when you built the collector. One row per successful input by default.
GET /dca/dataset?id=<collection_id> to retrieve the results of an asynchronous Bright Data Scraper Studio batch collection. While the collection is still running, the endpoint returns a status object. When the collection is ready, it returns a JSON array of records.
For the full trigger, poll and parse walkthrough in cURL, Python and Node.js, see the Quickstart.
Use the
collection_id returned by POST /dca/trigger as the id query parameter in this endpoint.Batch collection results are available for download for 16 days after collection. To avoid expiration, download the data within 16 days or configure a push delivery method to send it to your storage automatically.
Request
Response
While the collection is still building (HTTP 202):Retrieving results
While the collection is still running, the endpoint returns202 Accepted with a status object. When the collection is ready, it returns 200 OK with a JSON array of records.
For long-running collections, which can take minutes or hours, avoid frequent polling. Use one of these options instead:
- Check the collection status periodically with longer intervals.
- Configure a push delivery method, such as webhook, Amazon S3, Google Cloud Storage, Azure Blob Storage, SFTP/FTP or email.
- Use the dashboard to monitor run progress.
Errors
| Status | Cause | Fix |
|---|---|---|
401 Unauthorized | Token missing, malformed or revoked | Re-copy from Account Settings → API Tokens |
404 Not Found | Collection ID does not exist, was deleted or has expired (16 days) | Re-trigger the collector if the data is still needed |
[] (empty array) | Collection completed but produced no rows | Check the input URLs and the collector’s output schema |
5xx | Transient Bright Data API error | Retry with exponential backoff, for example 1s, 2s, 4s |
Related
- Trigger async batch collection: the endpoint that creates the collection
- Job data: job-level metadata (status, page counts, error counts)
- Get errors for a job: per-input error details
- Choose a delivery type: alternative to polling (webhook, S3, GCS, etc.)
Authorizations
Use your Bright Data API Key as a Bearer token in the Authorization header.
How to authenticate:
- Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users
- Include the API Key in the Authorization header of your requests
- Format:
Authorization: Bearer YOUR_API_KEY
Example:
Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07dfLearn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication
Query Parameters
Collection ID returned by POST /dca/trigger. Use this value as the id query parameter.
Example:
"j_abc123def456"
Response
Dataset (Ready)