Scraping API
Oxylabs Web Scraper API
Fetch public pages or use dedicated target parsers, with rendered HTML and asynchronous batch delivery.
Scraping API. Official documentation · Checked · Review due .
documented capabilities
HTTP API- Authentication
- Use Web Scraper API user credentials (USERNAME and PASSWORD) with HTTP Basic authentication.[1][5]
- Rendering and parsing
- render=html enables JavaScript rendering. Dedicated supported targets accept parse=true for structured JSON.[1]
- Delivery choices
- Realtime keeps the connection open; Push-Pull retrieves jobs asynchronously; Proxy Endpoint offers a proxy interface.[2]
- Batch size
- Push-Pull accepts up to 5,000 query or URL values per batch; Realtime and Proxy Endpoint do not support batch.[2]
- Screenshots
- render=png returns a Base64-encoded screenshot.[2]
Billing: Product-specific plan and target rates; exact costs and failed-request rules were not verified in this pilot.
Outputs: html, json, png
Documented for: Python Requests, Node.js, Curl
getting started
documentation reviewed- Create a Web Scraper API user in the dashboard.
- Choose universal plus a URL, or a supported dedicated source and query.
- Submit with Basic authentication; choose Realtime or asynchronous Push-Pull for the required delivery model.
Requirements & limitations
- Dedicated parsers apply to supported targets, not every arbitrary URL.
- Proxy Endpoint accepts fewer additional parameters than the HTTP integrations.
- Exact plan pricing and failed-request billing remain unverified.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
5 references- Web Scraper API product documentationChecked 2026-09-27
- Official Web Scraper API repositoryChecked 2026-09-27
- JavaScript rendering and browser controlChecked 2026-09-29
- Push-Pull jobs, callbacks and batch submissionChecked 2026-09-29
- Proxy Endpoint integration methodChecked 2026-10-26