Tools

Bright Data

Web Unlocker and SERP API through one direct endpoint
View as Markdown

Proxies Bright Data’s direct API — the single endpoint that fronts both Web Unlocker and the SERP API:

POST /brightdata   → https://api.brightdata.com/request

POST only. Every control travels in the JSON body ({zone, url, format, …}). The two products are distinguished by the zone field, not by the path.

The zone is filled in for you

The zone names your account’s Web Unlocker / SERP zone — account-specific config you have no way to know. So the gateway injects it when your body omits it. You can call /brightdata with just {url, format}:

  • If your body omits zone, the gateway adds the configured one.
  • If your body includes zone, the gateway respects it.

What the gateway injects and strips

Bright Data authenticates with the Authorization: Bearer header — the same header you use for your gateway token. So the gateway overwrites it with the injected Bright Data key:

  • The Authorization header is overwritten with the secret Bright Data key. Your gateway token is consumed by the gateway and never reaches Bright Data.
  • Bright Data has no query-param spelling of the key, so nothing is dropped from the query string.

Responses

Responses stream back untouched. With format: "raw", Bright Data returns the target site’s unprocessed bytes (HTML, JSON, sometimes binary) — the gateway forwards the exact bytes.

Example

$curl -X POST "$GATEWAY/brightdata" \
>  -H "Authorization: Bearer $TOKEN" \
>  -H "Content-Type: application/json" \
>  -d '{"url": "https://example.com", "format": "raw"}'

The response is Bright Data’s, returned unchanged. For request and response fields, follow Bright Data’s documentation — the gateway does not alter them.