Check Snapshot Status
Check whether a dataset snapshot is running, ready, or failed before downloading it.
Bright Data provides the world's #1 web data platform with Web Unlocker for bypassing anti-bot systems, SERP API for search engine data, and pre-made scrapers for popular websites. Collect any web data at scale.
Check whether a dataset snapshot is running, ready, or failed before downloading it.
Create a durable SERP API or Scraping Browser zone using a fixed safe plan. This Admin/Ops operation changes account infrastructure and may incur charges. If Bright Data returns HTTP 429, retry after the Retry-After delay when present.
Download a completed dataset snapshot. A pending response contains no result data; poll BRIGHTDATA_GET_SNAPSHOT_STATUS before retrying.
Create a billable filtered marketplace-dataset snapshot. Use records_limit to cap the number of included records.
Get current and pending Bright Data account balances. This endpoint requires an API key with Admin permission. If HTTP 429 is returned, retry after the Retry-After delay when present.
Retrieve enriched records plus available progress, cost, and provider metadata for a completed Deep Lookup request. Each record preserves the lookup's dynamic columns. If the API returns HTTP 429, retry according to Retry-After when present rather than using a fixed request rate.
Check a Deep Lookup request's status, progress, cost, and provider metadata. Poll until completion before retrieving results. If the API returns HTTP 429, retry according to Retry-After when present rather than using a fixed request rate.
Retrieve JSON or raw results for an asynchronous BRIGHTDATA_SERP_SEARCH request. A 202 response means the job is still pending and should be retried later.
Get a Web Archive search's status and its matching-file, dump-size-in-bytes, and dump-cost-in-USD estimates. The search only estimates a dump and does not create a billable dump. Up to 100 searches that have not had a dump triggered are allowed per day.
Get uploaded, downloaded, and total byte usage for one zone and date range. If HTTP 429 is returned, retry after the Retry-After delay when present.
Get invoice-aligned billed cost and bandwidth for one zone and date range. The `to_date` boundary is exclusive. If HTTP 429 is returned, retry after the Retry-After delay when present.
List static-network cities available for a country and proxy pool type.
List country codes available for each static proxy zone type.
List pre-built datasets in Bright Data's marketplace for structured scraping.
List account-owned Scraper Studio scrapers and discover collector IDs.
List configured Web Unlocker zones and their types for protected-URL scraping.
Scrape up to 20 input objects synchronously. Bright Data bills per returned record. Requests exceeding the one-minute synchronous limit fall back to an asynchronous snapshot; use the returned snapshot ID after retry_after seconds. On HTTP 429, honor the provider's Retry-After header before retrying.
Scrape a public URL through Web Unlocker when ordinary requests are blocked or require JavaScript rendering. Inspect returned content before retrying CAPTCHA pages.
Submit an asynchronous SERP search and return its response_id. Retrieve it with BRIGHTDATA_GET_SERP_RESULTS, selecting the same JSON or raw result format used here.
Search Bright Data's Web Archive and estimate matching files, dump size in bytes, and dump cost in USD. A search that exceeds 30 seconds returns only a search_id; pass it to BRIGHTDATA_GET_WEB_ARCHIVE_SEARCH until complete. The search itself estimates a dump and does not create a billable dump. Up to 100 searches that have not had a dump triggered are allowed per day.
Start an asynchronous Deep Lookup research request and return its request_id. Billing is $1 per matched record; the first 10 enrichment columns are included, each additional enrichment column costs $0.05, and skipped or unmatched records are free. The API may return HTTP 429; retry according to Retry-After when present rather than using a fixed request rate.
Start an asynchronous dataset or site crawl. Poll the returned snapshot_id with BRIGHTDATA_GET_SNAPSHOT_STATUS, then download it with BRIGHTDATA_GET_SNAPSHOT_RESULTS.
The Bright Data integration connects your Dench AI CRM directly to Bright Data, so agents can read and act on your Bright Data data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
22 actions are available for agents to invoke on your behalf. Every call runs through Bright Data's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Bright Data and click Connect — you'll authorize access through Bright Data's own sign-in flow. No API keys or code required.
Ask an agent to use Bright Data in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Bright Data integration connects your AI CRM to Bright Data, so AI agents can work with your Bright Data data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Bright Data integration currently exposes 22 actions, including Check Snapshot Status, Create Safe Zone, Download Snapshot Results, Filter Dataset, Get Customer Balance, and Get Deep Lookup Results. Agents invoke them on your behalf from chat or from automations.
No. You connect Bright Data from your Dench workspace using Bright Data's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Bright Data's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Bright Data connection from your workspace settings at any time.