Skip to main content
POST
Run a search
POST /webarchive/search searches the Bright Data Archive and returns either the full search result object or a search_id you poll for status.
Every search needs a time range. The filters object is required, and it must carry either max_age, or both min_date and max_date. A request with no filters object returns HTTP 400 with "filters" is required.

How to set the search time range

Use max_age for a window relative to now. Write it as a number followed by a unit: Bright Data recommends max_age of 24h for a first search, because recent data is delivered fastest.
Use min_date and max_date for a fixed calendar range. Both dates use YYYY-MM-DD format and both must be sent together.
Send one form or the other, never both. max_age combined with min_date and max_date in the same request is a conflict, and the results are undefined.
For date ranges older than 24 hours, use min_date and max_date rather than max_age. See Data range vs delivery time for how the requested range affects delivery speed.
If the search takes longer than 30 seconds, the response returns only a search_id and you should poll the status asynchronously. If the search completes within 30 seconds, the response returns the full search result object (same as GET /webarchive/search/<search_id>).
You can run up to 100 searches per day without triggering a dump. Once you trigger a dump, that search no longer counts against your limit.
  • Use LIKE filters (domain_like_*, url_like_*) for simple pattern matching with % (any sequence) and _ (single character).
  • LIKE patterns are case-insensitive and often faster than regex for simple prefix/suffix matching like %.com or amazon%.
  • Use regex filters (domain_regex_*, url_regex_*) for complex patterns requiring full regex syntax. LIKE patterns use backslash escaping: \% for literal %, \_ for literal _.

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:

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

Body

application/json
filters
object
required

Filters that scope the search. The filters object is required, and it must carry a time range: either max_age, or both min_date and max_date.

Response

Search initiated successfully

search_id
string

Returned if search is async

Example:

"ucd_abc123xyz"