-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Inaccurate Documentation & Missing Features in SDK (e.g., Web Scraper API)
Description
The documentation and resources provided by Bright Data appear to be incomplete or inaccurate, and the SDK is missing critical features that are either described or implied in the docs.
Issues Observed
-
Broken or outdated API reference – several documented endpoints either don’t match real behavior or are missing altogether.
-
SDK feature gaps – for example, to perform a simple Google Search you’d expect to use the SERP API or the SDK’s
search()helper, but neither works as described. -
The only working flow I found was to call the Web Scraper API directly with:
dataset_id = "gd_mfz5x93lmsjjjylob" url = "https://www.google.com" keyword = "<search-term>"
This approach is not reflected anywhere in the official docs or SDK.
-
The SDK has no support for the general
/triggerWeb Scraper API endpoint.- This prevents scraping sources like Trustpilot or G2, since the SDK exposes only a few mainstream scrapers.
- Ideally, the SDK should expose a generalized trigger/web-scraper function with built-in:
- rate-limit & retry logic
- error handling
- output validation
Current Workaround
The only reliable source of reference so far has been the Postman collection you provide; the official site documentation and the SDK don’t align with it.
Expected Behavior / Feature Request
- Ensure the documentation and API reference are up-to-date and consistent across the website, SDK, and Postman collection.
- Add generalized support for Web Scraper API
/triggerrequests to the SDK, including configurable rate-limit, retry, and error-handling logic.
Impact
These gaps make it difficult to implement even basic scraping workflows (e.g., Google, Trustpilot, G2) without writing custom request logic outside the SDK.