/scraping-api/ — Crawlbase Crawling API
Fetch page content with normal or JavaScript tokens, optional geo-routing and browser interaction controls.
Scraping API. Official documentation · Checked · Review due .
documented capabilities
HTTP API- Token types
- Normal tokens fetch static responses; JavaScript tokens enable browser rendering. javascript=true can switch a normal-token request to the JavaScript path.[1]
- Browser controls
- JavaScript requests support page_wait, ajax_wait, scroll and css_click_selector.[1]
- Extended scrolling
- The first 8 seconds of page-load plus scrolling count as one request; each additional started 5-second interval adds one billed request.[1]
- HTTP-method limitation
- POST is supported with the normal token only; JavaScript-rendered requests use GET.[1]
Billing: Successful requests; JavaScript request configuration and extended scrolling affect billed usage.
Outputs: html, json
Documented for: Python, Node.js, Curl
[ official reference ][ provider discussion ][ JSON record ]
getting started
documentation reviewed- Obtain the normal and JavaScript tokens from the account.
- Call the Crawling API with token and target URL.
- Use JavaScript-specific waits or scrolling only when necessary and budget for extended scrolling.
Requirements & limitations
- Exact dollar rates, account concurrency and complete failed-response billing rules remain unverified.
- Do not assume a long scroll costs the same as one short fetch.
- SDK compatibility is documented rather than executed.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
1 references- Crawling API token, request and scrolling documentationChecked 2026-09-27