cURL
Account Management API
Add a zone
Use the Bright Data Account Management API to add a Zone. POST /zone returns 200 OK with zone or account configuration data as JSON.
POST
cURL
ISP proxy zone examples
Creating an ISP zone requires specific parameter combinations. The fields below are not optional. Omitting them will silently create the wrong zone type or billing plan.Shared ISP (pay-per-GB)
Shared ISP (unlimited bandwidth)
Settingbandwidth: unlimited alone does not activate unlimited billing. You must also include unl_bw_tiers: std.
Dedicated ISP (unlimited bandwidth)
Residential proxy zone
Creating any Residential proxy type (shared rotating, IPv6 or dedicated) after July 7, 2026 requires KYC approval by the Bright Data compliance team. There is no automatic or no-KYC path for these new zones. Without KYC, create an ISP or Datacenter zone instead.Dedicated Residential (gIP) zone
A dedicated Residential zone allocates a gIP (group of IPs) that is exclusive to a fixed list of target domains. Create one by settingvips_type: "domain" and including domain_whitelist.
The following payload creates a dedicated Residential zone with one US gIP scoped to example.com. This payload was verified working on July 9, 2026.
domain_whitelist. Requests to any other domain are routed through Bright Data’s shared Datacenter proxies.
Shared Residential country targeting
For shared Residential zones, country is not set withvip_country. Target countries at request level with the -country-<code> flag in the proxy username (for example -country-us), or set default countries in the control panel. See How to configure your Residential proxy.
Dedicated Residential gIP errors
An invalid dedicated Residential (gIP) payload returns one of the following errors.Residential 403 compliance errors
For Residential zones created after July 7, 2026, an Add-a-Zone request from an account that is not eligible returns HTTP 403 with one of the following compliance errors. Zones created on or before July 7, 2026 are not affected. See the proxy errors catalog for the full catalog.
Each error returns a structured JSON body so integrations can branch on the stable
code value. A company-email account without KYC receives kyc_required:
business_account_required, which does not offer KYC because personal accounts are not eligible:
alternatives array with the exact plan objects to create a no-KYC ISP or Web Unlocker API zone instead. To create the ISP zone, send POST /zone with that plan object in place of the Residential one.Authorizations
Use your Bright Data API Key as a Bearer token in the Authorization header.
How to authenticate:
- Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users
- Include the API Key in the Authorization header of your requests
- 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
Response
201
Zone added