Bright Data Access Bootstrap

Overview

Establish the product, identity, zone, target, and secret boundaries before any live collection. Native proxy clients use a zone username/password, while REST API clients use a named-user API key; treat them as different credentials with different blast radii.

Prerequisites

• An approved public-data purpose and target allowlist
• A Bright Data account owner who can grant only the required product and zone
• A secret manager and a non-production validation environment

Instructions

Step 1: Inventory the access path

Read the integration and Grep for existing Bright Data hosts, environment names, and secret references. Classify each call as native proxy, Browser API, or REST API before choosing credentials.

Step 2: Define the secret contract