Bright Data · Authentication Profile

Brightdata Authentication

Authentication

Bright Data secures its APIs with http and userPassword across 2 declared security schemes, as derived from its OpenAPI definitions.

Web DataWeb ScrapingWeb IntelligenceProxyData ExtractionSERPWeb UnlockerDatasetsData CollectionBrowser Automation
Methods: http, userPassword Schemes: 2 OAuth flows: API key in:

Security Schemes

api_token http
scheme: bearer
zone_credentials userPassword

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-12'
method: derived
source: openapi/brightdata-openapi.yml
summary:
  types:
  - http
  - userPassword
schemes:
- name: api_token
  type: http
  scheme: bearer
  bearerFormat: apiKey
  description: >-
    Bright Data platform API token from the control panel, sent as
    'Authorization: Bearer <API_KEY>' on all api.brightdata.com REST calls
    (Web Scraper, SERP, Web Unlocker, Zones, Browser API session).
  sources:
  - openapi/brightdata-openapi.yml
- name: zone_credentials
  type: userPassword
  description: >-
    Proxy and Scraping Browser zones authenticate with zone credentials
    (username 'brd-customer-<CUSTOMER_ID>-zone-<ZONE>' and the zone password).
    For the Scraping Browser these are embedded in the CDP WebSocket URL
    userinfo ('wss://...@brd.superproxy.io:9222'); for proxy traffic they are
    sent as HTTP(S)/SOCKS proxy credentials against brd.superproxy.io.
  sources:
  - asyncapi/brightdata-asyncapi.yml