/scraping-api/ — ScraperAPI
A scraping HTTP API with optional rendering, premium proxy pools and asynchronous requests.
Scraping API. Official documentation · Checked · Review due .
documented capabilities
HTTP API- Rendering
- render=true returns HTML after JavaScript execution; wait_for_selector requires rendering.[1]
- Credit examples
- The documented parameter table lists 10 credits for rendering, 25 for premium plus rendering, and 75 for ultra-premium plus rendering.[2]
- Billable outcomes
- HTTP 200 and 404 responses are charged, as are client-cancelled requests when the client allows less than 70 seconds.[2]
- Cost inspection
- The account/urlcost endpoint estimates request cost and the sa-credit-cost response header reports actual credits.[2]
- Concurrency
- Concurrency is plan-dependent; the Async API supports batch requests.[3]
Billing: API credits determined by target domain and request options.
Outputs: html, json
Documented for: Python Requests, Node.js, Curl
[ official reference ][ provider discussion ][ JSON record ]
getting started
documentation reviewed- Get an API key and select synchronous, asynchronous or proxy access.
- Send the target URL and request options with the API key.
- Check target-specific cost before a batch and allow the documented timeout before cancelling.
Requirements & limitations
- The listed rendering credits are configuration examples; protected domains and special targets can change total cost.
- A target 404 can still be billed.
- Unused subscription credits do not roll over.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
3 references- Supported request parametersChecked 2026-09-27
- Credits and request costsChecked 2026-09-27
- API, async and concurrency FAQChecked 2026-09-27