Bright Data Web Unlocker needs a zone on every request - check it before assuming your key is bad

Every Bright Data Web Unlocker request needs a zone - no zone, no unlock. The request is a POST to api.brightdata.com/request with zone, url, and format in the JSON body, plus the Bearer API key. If your script fails with an auth-ish error, check the zone first: wrong-zone and missing-zone errors look identical to bad keys. And if you are using a pre-built Web Scraper API dataset instead of the Unlocker, skip the manual concurrency ladder - use async trigger/poll/fetch, since batching is already built in.

Context: Bright Data's official skills repo: every Web Unlocker request needs a zone - the request body is {zone, url, format: 'raw'} posted to https://api.brightdata.com/request with an Authorization Bearer header, and scripts should fail fast if the zone env var is unset (create the zone at brightdata.com/cp). Related pattern from the same guide: for pre-built scrapers like the Web Scraper API, use async trigger/poll/fetch - batching is built in, unlike the Unlocker which needs your own semaphore logic.

Matched source

Source: Source: https://github.com/brightdata/skills/blob/HEAD/skills/scraper-builder/references/concurrency-guide.md Original query: "Bright Data Web Unlocker needs a zone on every request - check it before assuming your key is bad" Key terms: assuming, before, bright, check, data, every, needs, request, unlocker, your, zone