Skip to main content
GET
/
dca
/
log
/
{job_id}
cURL
curl --request GET \
  --url https://api.brightdata.com/dca/log/{job_id} \
  --header 'Authorization: Bearer <token>'
{
  "Id": "j_ma13y9ay1piehrso8r",
  "Status": "done",
  "Collector": "c_m9im5n7v82p2y35la",
  "Template": "t_m9jty150kxgwtzcgi.3",
  "Inputs": 1,
  "dup_inputs": 0,
  "Lines": 60,
  "Fails": 0,
  "Pages": 1,
  "Pages_left": 0,
  "Success": 1,
  "Navigations": 2,
  "created": "2025-04-28T13:22:16.857Z",
  "started": "2025-04-28T13:22:17.502Z",
  "finished": "2025-04-28T13:23:28.961Z",
  "trigger": "amite@brightdata.com",
  "Success_rate": 1,
  "Job_time": 71459,
  "Queue_time": 645
}

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.

Retrieve metadata for a triggered Bright Data Scraper Studio job: status, input counts, success and failure counts, page counts and run timestamps. Use this endpoint when you need observability into a job, for example to track how many inputs succeeded, how many failed or how long the job took. This endpoint returns metadata only. To download the actual scraped data, use Receive batch data.

​
Request

The job_id is the collection_id returned by POST /dca/trigger. 
curl "https://api.brightdata.com/dca/log/$JOB_ID" \
  -H "Authorization: Bearer $BRIGHT_DATA_API_TOKEN"

​
Response

{
  "Id": "j_ma13y9ay1piehrso8r",
  "Status": "done",
  "Collector": "c_m9im5n7v82p2y35la",
  "Template": "t_m9jty150kxgwtzcgi.3",
  "Inputs": 1,
  "dup_inputs": 0,
  "Lines": 60,
  "Fails": 0,
  "Pages": 1,
  "Pages_left": 0,
  "Success": 1,
  "Navigations": 2,
  "created": "2026-05-22T13:22:16.857Z",
  "started": "2026-05-22T13:22:18.123Z"
}
Common Status values: building, running, done, failed, cancelled.

​
When to use this endpoint

  • Track job progress for a dashboard or monitor
  • Compute a success rate: Success / Inputs
  • Identify which jobs deduplicated inputs (dup_inputs > 0)
  • Measure job duration: compare started to the response timestamp
For the actual scraped records, see Receive batch data. For per-input error details, see Get errors for a job.

​
Errors

StatusCauseFix
401 UnauthorizedToken missing, malformed or revokedRe-copy from Account Settings → API Tokens
404 Not FoundJob ID does not exist or has expiredConfirm the ID matches a recent collection_id from /dca/trigger
5xxTransient Bright Data API errorRetry with exponential backoff, for example 1s, 2s, 4s

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

Path Parameters

​
job_id
string
required

The ID of the job to retrieve.

Response

200 - application/json

OK