When Bright Data fits
An authorized retrieval workload needing an explicit zone configuration and a clear boundary between page access and structured platform-specific extraction.
Check before integrating
Web Unlocker, Browser API, SERP API and Web Scraper API are different products. A successful HTML retrieval is not proof that a structured product record is correct.
Provider endpoint reference
This is Bright Data's documented interface. Its credentials and response format are separate from an All Them APIs account.
POST https://api.brightdata.com/request
Authentication: Bearer API token and configured zone
Inputs: JSON zone, url and format for the configured product
Output: Raw content or a wrapped response according to format and zone configuration.| Capability | What to expect |
|---|---|
| Primary workflow | Zone-based Web Unlocker retrieval |
| Returned content | Raw content or response wrapper; other formats depend on product |
| Rendering/control | Interactive browser work is a separate Browser API |
| Job model | Synchronous retrieval; asynchronous option also documented |
| Integration boundary | Choose and configure the correct product/zone |
| Cost driver | Product, zone and successful-request rules |
Pricing model and production access
Product-specific usage and successful-request pricing. Price the selected Web Unlocker zone and output. Do not compare proxy bandwidth, a scraper dataset and an Unlocker request as if they were one billing unit.
For 1,000 accepted pages, record attempted URLs, render mode, retries and schema failures. A low HTML-request price can require separate parsing; an extraction credit can include work that another vendor bills separately. Do not rank cost until the output passes the same acceptance check.
Migration notes
Separate zone configuration from your public request schema. Do not route an interactive login task to Web Unlocker or assume its response matches a structured Web Scraper dataset.
Keep provider-specific authentication and response mapping inside an adapter. Preserve source timestamps and identifiers so changing a provider does not silently change the meaning of stored records.
Bright Data alternatives
| Alternative | When to evaluate it |
|---|---|
| Bright Data vs Firecrawl | An agent or retrieval pipeline that wants main-content documents without building a separate HTML-to-Markdown stage. |
| Bright Data vs ScrapingBee | A team that wants to start with page retrieval and add explicit wait conditions or selector-based extraction. |
| Bright Data vs ScraperAPI | An existing HTTP collection pipeline that wants managed page retrieval while retaining its own parsing and validation. |
| Bright Data vs Zyte API | A collector that needs to choose between raw HTTP retrieval, rendered content and structured extraction while retaining request-level controls. |
| Bright Data vs Apify | A recurring or site-specific collection job that benefits from an existing Actor or a custom hosted scraper. |
A fair evaluation
- Build an authorized test set spanning static HTML, JavaScript-rendered pages, tables and long articles. Save expected fields and the permitted access conditions.
- Use the same URLs, country, device settings and freshness window. Keep cache hits separate from fresh fetches.
- Mark challenge pages, empty main content and invalid structured fields as failures even if the HTTP status is 200.
- Measure time to a usable document or completed dataset, not only time to job creation. Include polling, retries and client-side parsing.
- Report total billed credits, browser time, proxy charges and actor fees per accepted document. Respect site terms, privacy, robots guidance and access controls; do not test bypassing protected accounts.
A common integration contract
POST /api/v1/web-scraping/extractReview the request contract and tell us the coverage you need. Access requires enablement; this endpoint does not execute or bill requests yet.
View endpoint and request accessSources and review dates
Documentation reviewed October 28, 2026. These are integration and plan comparisons, not measured speed or accuracy rankings. Availability, licensing and prices should be confirmed for the chosen plan.
Corrections: email faizank@docsalot.dev with an official source.