ScraperAPI review for web scraping without the proxy work

What the ScraperAPI web scraping API is

ScraperAPI is a web scraping API. You send it a URL and an API key, and it returns the page as raw HTML or structured JSON after dealing with the parts that usually break a scraper: rotating proxies, headers, retries, CAPTCHAs and anti-bot checks. The company says it started in 2018 as a one-person project and now serves more than 10,000 brands, which is its own figure.

It is a developer tool. ScraperAPI offers a dashboard and a crawler UI, but the core product is an endpoint you call from code.

Who it is for, and who should skip it

It suits developers, data teams and agencies who scrape public sites at steady volume for price monitoring, SEO data, lead lists or research, and who would rather pay per request than run proxy pools and headless browsers themselves. It is a good fit for ecommerce targets like Amazon, Walmart and eBay, which have their own credit rate and structured data endpoints.

Skip it if you need a no-code point-and-click scraper, or if your volume is mostly Google results or LinkedIn pages. Those take 25 and 30 credits per request, and the entry tiers run out fast. Also skip it if you were hoping an API would solve the legal side of scraping. It handles access, not permission.

Key features, from request to raw HTML response

The basic flow is simple: grab your API key, call the endpoint with the target URL, and add parameters as needed. The documentation covers four ways in:

• Synchronous API: a single GET to the endpoint, or the proxy port method if your scraper already expects a proxy. POST and PUT requests are supported.
• Asynchronous API: submit jobs and batch requests, then collect results or receive them by callback. This is the better choice for large or slow targets.
• Structured data endpoints: ready-made JSON for ecommerce, search, real estate and AI results, plus an AI Parser for other pages.
• DataPipeline and Crawler: scheduled scraping projects and a crawler (version 2.0) with its own UI and API, for teams that want jobs run without writing the loop themselves.

Every plan includes JS rendering, premium proxies, JSON auto parsing, custom headers and sessions, desktop and mobile user agents, automatic retries and unlimited bandwidth. The vendor also advertises a 99.9% uptime guarantee. Useful controls include geotargeting by country code, sticky sessions, cached responses and a max_cost parameter that caps what a single request can spend. Each response carries an sa-credit-cost header, and a Domain Cost Estimator in the dashboard (or a urlcost API endpoint) tells you the price of a URL before you scrape it. The docs also list SDKs, LLM integrations and automation and workflow integrations.

ScraperAPI pricing, plans and free trial

Prices checked 29 Oct 2026, in USD. The ScraperAPI free trial needs no card, and annual billing saves 10% on every self-serve tier.

Credits do not roll over on any plan. When you run out, Hobby, Startup and Business pause until renewal unless you opt in to auto-upgrade, which moves you to the next plan. Scaling and above can also switch on pay-as-you-go at a fixed per-credit rate, up to a monthly cap you set. You can cancel from the dashboard with no cancellation fee, and the pricing FAQ promises a 7-day no-questions-asked refund.

What a ScraperAPI credit buys per request

This is the part to read before picking a tier, because ScraperAPI credits are not all equal. ScraperAPI charges 1 credit for a standard page. Amazon, Walmart and eBay cost 5, Google and Bing cost 25, and LinkedIn costs 30. Requests that need a Cloudflare, DataDome, PerimeterX or Akamai bypass cost 10 credits, and so do JS rendering, premium proxies and screenshots. Premium proxies plus rendering cost 25, and Ultra Premium costs 30, or 75 with rendering, on paid plans only. Geotargeting, sessions, device type and output format cost nothing extra.

So the $49 Hobby plan covers about 100,000 plain pages (roughly $0.49 per 1,000), 20,000 Amazon product pages, 10,000 rendered pages or 4,000 Google searches a month (about $12.25 per 1,000). On Startup, the same Google request works out at about $3.73 per 1,000. Failed requests are not charged; only 200 and 404 responses count. Going over your concurrency limit returns a 429 error rather than a bill. Protected and search targets are where it gets expensive, so check the credit costs for your own URL list first.

What users say

ScraperAPI holds 4.6 out of 5 from 62 GetApp reviews (Oct 2026), with ease of use at 4.9, value for money 4.5 and customer support 4.6. Reviewers mention quick setup, clear documentation and good results on difficult sites. The complaints are consistent too: some want credit rollover and cheaper premium features, and a few report slow responses, failed requests or trouble with specific sites. The Trustpilot profile shows mostly positive reviews, but Trustpilot notes the company has not invited reviews recently, so they may not be representative.

Company, proxy network and integrations

ScraperAPI is cloud-only, used through its API, dashboard and crawler UI, with code examples in cURL, Python, Node.js, PHP, Ruby and Java. The about page lists Zoltan Bettenbuk as CTO and dates the first version to 2018. The vendor says customers send 36 billion requests a month. Invoices, VAT numbers, payment methods, cancellation and account deletion are all handled in the dashboard, according to the docs. The pages checked do not list security certifications such as SOC 2.

What changed recently

ScraperAPI has acquired Traject Data, the company behind the Rainforest API and SerpWow API. A blog post dated 30 April 2026 says the deal closed a few months earlier and that existing service, pricing and API keys stay the same while Traject's structured data APIs move onto ScraperAPI's infrastructure. The current pricing also adds limited-time bonus credits to the Professional and Advanced plans.

Limits and drawbacks of this scraper API

• The credit multipliers make the headline ScraperAPI credits misleading for search, social and protected targets.
• No rollover, so a quiet month is money lost.
• Overage billing is only available from Scaling upward, and country-level targeting from Business upward.
• Priority support starts at the $975 Professional plan.
• Scraping legality and target-site terms remain your responsibility.

Alternatives to ScraperAPI worth testing

Each alternative to ScraperAPI below does the same basic job. Compared to ScraperAPI, the differences are mostly in pricing model, ready-made scrapers and proxy access.

• Apify: pick it if you want ready-made scrapers (Actors) for specific sites and scheduling in one platform, not just a raw request API.
• ScrapingBee: a close like-for-like scraping API with JS rendering and proxies; worth comparing if your credit mix differs from ScraperAPI's.
• Zyte API: pick it if you run Scrapy already and want a scraping API from the team behind it.
• Bright Data: pick it for very large jobs or when you need direct access to residential and mobile proxy networks with enterprise contracts.
• Firecrawl: pick it if the pages are headed into an LLM and you want clean markdown output and site crawling out of the box.

Verdict

ScraperAPI does one job well: it turns a URL into usable HTML or JSON without you maintaining proxies or browsers, and the cost controls are better than most. I would use ScraperAPI for ecommerce and general site scraping at steady volume. For mostly Google or LinkedIn work, I would price the job against an alternative first, because the 25 and 30 credit rates change the maths a lot.