Affiliate disclosure: We earn a commission if you sign up through our links. This does not influence our test results or editorial scores. Full disclosure →

ScraperAPI Review (2026): Verdict, pricing and what the credit math actually costs

Last tested: 2026-01-15 · WebScrapingTool.net editorial team

METHODOLOGY

How we tested ScraperAPI

3 target sites

Shopify product page (static), LinkedIn profile (logged-out), Google SERP (JavaScript-rendered)

1,000 requests per target

Soak test over 72 hours. Success = 200 response with expected CSS selector present in the body.

What we measured

Success rate %, credits consumed per request, realised cost per 1,000 records, average response time (ms).

Last test run: January 2026. We retest quarterly. Results may vary based on target site changes. Full methodology →

Verdict 8.5/10

Best for

✓ Indie founders with a curl loop and a deadline

Skip if

✗ Protected e-commerce at >100K req/day or enterprise compliance requirements

Price floor

$49/mo Hobby (20K credits)

Realism: A 50,000-request/month protected e-comm workload runs ~$300/mo here, vs ~$240/mo on Zyte and ~$180/mo on Scrape.do at lower success.
Try ScraperAPI → Read methodology →

ScraperAPI — verdict: best for the indie founder with a curl loop and a deadline. Skip if you’re scraping protected e-commerce at >100K req/day.

ScraperAPI’s Hobby tier ($49/mo, 20K credits) is the most “I-tried-it-and-it-just-works” experience in the API category — the integration is two query parameters added to a URL, and the documentation respects your time. On a static-HTML target (a non-protected Shopify product page), we measured 96% success in our 1,000-request soak. On a protected target (an Akamai-fronted retail site), the success rate dropped to 71% and credits-per-request rose from 1 to 5 — that 5× math is what surprises the buyer at week 2.

Hands-on test: what the integration looks like

Here’s the full integration. Two query parameters:

ScraperAPI — basic request
curl "https://api.scraperapi.com/?api_key=YOUR_KEY&url=https://example.com/product-page"

For JavaScript rendering, add render=true:

ScraperAPI — JavaScript rendering
curl "https://api.scraperapi.com/?api_key=YOUR_KEY&url=https://example.com/spa&render=true"

Python integration is one function call:

ScraperAPI — Python
import requests

payload = {
  'api_key': 'YOUR_KEY',
  'url': 'https://www.amazon.com/dp/B09XYZ'
}
r = requests.get('https://api.scraperapi.com', params=payload)
print(r.text)  # Raw HTML, as if a real browser fetched it

That’s it. No SDK to install, no proxy credentials to configure. If your existing code uses requests.get(url), you change one line.

Test results: our Jan 2026 soak

We ran 1,000 requests per target over 72 hours. “Success” = 200 response with the expected CSS selector present in the body.

TargetSuccess rateCredits/requestCost/1K records
Shopify static product96%1$1.20
LinkedIn profile (logged-out)11%10$24.50
Google SERP78%10$6.10

The LinkedIn number is the one that matters. ScraperAPI’s documentation doesn’t hide it: LinkedIn is explicitly listed as a “hard target” requiring their premium_proxies=true parameter — and even then, success is low. If LinkedIn data is your use case, ScraperAPI is not the tool. Bright Data’s LinkedIn scraper or an Apify actor for LinkedIn is the correct call.

The Google SERP number (78%) with 10 credits per request means you’re paying $6.10 per 1,000 SERP results. Compare to Bright Data’s SERP API at $3/1K — roughly 2× more expensive on ScraperAPI for the same output.

Pricing: what you’re actually buying

ScraperAPI has four main tiers as of January 2026:

PlanPrice/moCreditsNotes
Hobby$4920KGood for dev/testing. 5 concurrent connections.
Startup$149100KThe sweet spot for production S1 workloads.
Business$299500K1M credits if you need rendering.
Enterprise$4993MCustom on request above this.

The credit multiplier is the number to understand. Simple static-HTML requests cost 1 credit. JavaScript-rendered pages cost 5 credits. Premium proxies (higher-success on protected targets) cost 10–25 credits per request.

A real-world protected e-commerce workload (say, scraping 50K Akamai-fronted product pages per month):

  • At 5 credits/request: 250K credits/month
  • At the Startup tier ($149/mo, 100K credits), you’d need the Business tier ($299/mo, 500K credits)
  • Realised cost: ~$300/mo for 50K pages at 71% success

Compare: Zyte at ~$240/mo for the same workload at 94.3% success (per Firecrawl’s 2025 benchmark). The credit-per-request math turns against ScraperAPI above $200K credits/month on protected targets.

DIY → API

Where DIY hits the wall

If you used to Google "node js web scraper", you're in the right place. The market shifted. DIY-tutorial keywords are down 63–88% YoY — not because demand died, but because ChatGPT writes the scraper and Cloudflare Turnstile breaks it three days later. The solo developer buying ScraperAPI at $49/mo is not replacing a Scrapy pipeline — they're replacing a weekend they don't have. Here's where the wall is, and what to buy instead.

Find the right API in 60 seconds →

Pros and cons

What works:

  • Five-line integration. Your existing code doesn’t need refactoring.
  • Documentation is honest about limitations (hard targets are named).
  • 96% success on static HTML is industry-leading for the price tier.
  • Residential proxy pool handles most Shopify/WordPress/basic SPA targets.
  • $49/mo Hobby is genuinely useful for development and prototyping.

What doesn’t:

  • The 5×–25× credit multiplier catches buyers at week 2. Budget for this before signing.
  • Black-box failure mode: when requests fail on protected targets, the error gives you 403 or 521 with no actionable detail.
  • LinkedIn success rate (11%) is not competitive. Don’t buy ScraperAPI for LinkedIn scraping.
  • No DPA on file as of January 2026. Acceptable for personal projects; not for GDPR-scoped enterprise use.
  • Above 1M req/mo, the math points to Zyte or Oxylabs.

Alternatives by use case

  • Scraping protected e-commerce at >$300/mo budget: Try Zyte — 94.3% measured success at lower cost/record.
  • No-code requirement: Apify — actor marketplace with 8,000 pre-built scrapers.
  • Free tier for development: ScraperAPI has a 1K-credit free trial. Apify has $5 credit free. Octoparse has a free desktop tier.
  • LinkedIn specifically: Official LinkedIn API, or Apify’s LinkedIn actors (which comply with LinkedIn ToS at reduced volume).
  • SERP data: Bright Data’s SERP API at $3/1K is approximately 2× cheaper than ScraperAPI for Google results.

FAQ

Does ScraperAPI have a free trial?

Yes. 1,000 credits free, no credit card required. Sufficient to test on your target site before committing.

Is ScraperAPI good for beginners?

Yes — it’s the best beginner API in the market for the “I need to scrape one site and I know Python” use case. The two-parameter integration means zero setup time. The documentation is clear about what it can and can’t do.

What is a ScraperAPI credit?

One credit = one HTTP request at standard resolution. JavaScript-rendered requests cost 5 credits. Requests through premium proxies (for harder targets) cost 10–25 credits. The credit model is documented in their pricing page.

Does ScraperAPI rotate proxies automatically?

Yes. Residential proxy rotation is included in all tiers. You don’t configure proxy credentials — the API handles it.

How does ScraperAPI handle CAPTCHAs?

It uses CAPTCHA bypass for common challenge types (reCAPTCHA v2/v3, hCaptcha) on protected-target requests (premium_proxies=true). Not 100% effective on enterprise anti-bot (DataDome, Akamai Intelligent Platform) — that’s why the success rate drops to 71% on our Akamai test.

Go deeper

🧭 Decision wizard