FAQ

The questions every ScrapeIt integration asks first. Can't find yours? The Quickstart and product references cover the details, and support is one click away in the dashboard.

How many credits does a scraping request cost?

A fetch through a datacenter proxy costs 4 credits and a browser render 30; through a residential proxy 15 and 50. Site APIs cost one flat price per request, and a cache hit costs half. Every Web Scraping API response reports cost.estimated_credits and cost.charged_credits, and every site API response meta.cost.charged_credits. Price list: Request cost.

How do I authenticate API requests?

Send your API key in the x-api-key header (recommended) or as Authorization: Bearer sk_.... Keys start with sk_, are shown once at creation and can be scoped per product. Details: Authentication & API keys.

How do I choose the proxy type and country?

Set proxyType to datacenter, residential or auto (the platform picks the tier and moves to residential on a block) and proxyCountry to an ISO-3166 alpha-2 code such as US or DE. ScrapeIt routes the request through a healthy proxy of that class and geography. Details: Proxy options.

How do I scrape JavaScript-heavy websites?

By default (jsRendering omitted or "auto") ScrapeIt fetches the page first and renders it in a managed remote browser only when it needs one - an empty page, a single-page-app shell, an anti-bot challenge (auto rendering). Set jsRendering to true to always render; combine it with wait, waitFor and jsScenario steps for dynamic pages, or captureNetwork to harvest the JSON APIs a single-page app calls. Details: JavaScript rendering.

How do I verify a webhook came from ScrapeIt?

Compute HMAC-SHA256 over "<x-scrapeit-timestamp>.<raw request body>" with your endpoint signing secret and compare it to the x-scrapeit-signature header value after the v1= prefix, using a constant-time comparison. Ready-made Node.js and Python verifiers: Webhooks.

What happens when a webhook delivery fails?

ScrapeIt retries the delivery automatically after 30 seconds, 2 minutes and 10 minutes (4 HTTP attempts in total). After that the delivery is dead-lettered; you can inspect and retry it manually from the dashboard or the deliveries API. Details: Retries & dead-lettering.

Does the shared cache make repeated requests cheaper?

Yes. A request served from the shared cache responds faster and costs half the normal credits. Only successful HTTP 200 responses are stored in the cache. Details: Cache options.

What does HTTP 429 concurrency_limit_exceeded mean?

Your plan allows a fixed number of concurrent scraping requests. When all slots are busy new requests are rejected with HTTP 429 before any work starts. Retry after an active request finishes or upgrade the plan. Details: Concurrency & limits.

Is there a ready-made scraper for apartments.com?

Yes. The Apartments.com Scraper API returns normalized rental data without any selectors of your own: a Listing API that searches a city with the site's own filters, a Property API that returns full detail (floor plans, units, fees, amenities, walk/transit scores, leasing-office contact), and a no-code scraper that exports the same records to JSON, CSV and XML.