Skip to main content
POST
/
dca
/
trigger
curl --request POST \
  --url 'https://api.brightdata.com/dca/trigger?collector=c_abc123' \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '[{"url": "https://example.com/product/1"}]'
{
  "collection_id": "ID_DATASET",
  "start_eta": "2021-11-07T13:26:22.702Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.brightdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Queue a published Bright Data Scraper Studio collector to run against one or more inputs. The endpoint returns a collection_id immediately. Poll the Receive batch data endpoint with that ID until the dataset is ready. For the full happy-path walkthrough (auth, trigger, poll, parse) in cURL, Python and Node.js, see the Quickstart. This page is the parameter and error reference.

​
Request

The request body is a JSON array of input objects. Each object must match the input schema you defined when you built the collector in Scraper Studio. The default schema is a single url field. 
curl -X POST \
  "https://api.brightdata.com/dca/trigger?collector=$BRIGHT_DATA_COLLECTOR_ID&queue_next=1" \
  -H "Authorization: Bearer $BRIGHT_DATA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '[{"url": "https://www.dm.de/p/d/3133774/babylove-teller-silikon-mit-trennschale-regenbogen-orange-creme"}]'

​
Response

{
  "collection_id": "j_abc123def456",
  "start_eta": "2026-05-22T13:26:22.702Z"
}
The collection_id is the snapshot identifier. Pass it to /dca/dataset?id=<collection_id> to poll for results. See the Quickstart for how the IDs relate to one another.

​
Errors

StatusCauseFix
401 UnauthorizedToken missing, malformed or revokedRe-copy from Account Settings → API Tokens
404 Not FoundCollector ID does not exist or your account does not have accessOpen the collector in Scraper Studio and re-copy the ID
422 Unprocessable EntityThe objects in your request body do not match the collector’s input schemaConfirm field names against the Inputs tab of your collector
5xxTransient Bright Data API errorRetry with exponential backoff, for example 1s, 2s, 4s

​
Retry behavior

Re-triggering the same inputs creates a new collection with a new collection_id. The endpoint is not idempotent and there is no de-duplication across triggers. To retry only the failed inputs from a previous run, use Get errors for a job to identify them, then trigger a new collection with just those inputs.

Authorizations

​
Authorization
string
header
required

Use your Bright Data API Key as a Bearer token in the Authorization header.

How to authenticate:

  1. Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users
  2. Include the API Key in the Authorization header of your requests
  3. Format: Authorization: Bearer YOUR_API_KEY

Example:

Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07df

Learn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication

Query Parameters

​
collector
string
required

A unique identification of scraper

​
version
string

Set to dev to trigger the development version of the scraper

​
name
string

human_name - A human readable name for the batch

​
queue_next
integer
default:1

If there's already something in the crawl queue, push this job into the queue

​
queue
string

Send another batch of requests that will start after the last one is finished

​
confirm_cancel
integer
default:1

Cancel running job and run instead, submit the request and cancel running one

​
no_downloads
integer
default:1

Disable media file download

​
deadline
string

Set job time deadline, job will be terminated after specified time. h for hours, m for minutes, s for seconds.

Body

application/json
​
url
string<uri>

Response

200 - application/json

OK