Web Scraping API
Web Scraping API is JoyProxy’s managed data-collection service. You submit a target URL. In the cloud, JoyProxy handles real-browser emulation, proxy rotation across 150+ countries, JavaScript rendering, and common anti-bot protections, then returns clean HTML or structured JSON.
Unlike Rotating Proxies or Static Proxies, Web Scraping API does not require you to run a proxy pool, User-Agent rotation, or a headless browser farm. Billing is success-only: Credits are deducted only when the fetch succeeds.
Proxy IPs vs Web Scraping API
| Comparison | Proxy IPs (Rotating / Static / Custom) | Web Scraping API |
|---|---|---|
| What you get | A proxy endpoint Host:Port | A managed HTTP API that returns the target page HTML / JSON |
| Ops cost | You maintain cookies, User-Agent, and Playwright/Puppeteer browser farms | Zero ops — JoyProxy handles rendering, retries, and anti-bot |
| Billing | Per-GB traffic or dedicated IP/port time | Credits on success only — failed, timed-out, or hard-blocked fetches are not charged |
| Best for | Mature crawlers that only need a network exit | Getting page content or structured data without running a browser cluster |
Key advantages
- Success-only Credits (no charge on failure): Credits are deducted only when the response is HTTP 2xx and the body contains valid content. If the target errors, times out, or blocks the request, no Credits are charged.
- Managed JS rendering and anti-bot bypass: Pass
render=trueto enable cloud headless rendering. Passsuper=trueto route through real residential/mobile exits for high-risk targets. - Structured data Plugins: Dedicated plugins for Amazon, Google Search, Google Maps, YouTube, and more return formatted JSON.
- Sync and Async API: Millisecond-level synchronous requests, plus an async queue for large batches.
In this chapter
Read in this order if you are new:
- Quick start — 4-step setup and Scraping API Token
- Buy credit packs and concurrency — credit packs and Concurrency rules
- Test a fetch in API Center — try requests in API Center and copy integration examples
- Fetch parameters and credit usage — render / super / geoCode and 1 / 5 / 10 / 25 credit costs
- Structured data plugins API — JSON plugins for commerce and search
- Async queue API — submit and poll large or long-running jobs
- Usage and fetch logs — Usage dashboard and recent requests
- Response codes and errors — 401 / 402 / 429 / 502 and how to confirm zero charge
- Restricted targets and compliance — destinations the API will not fetch
- Payments and invoices — order history and PDF invoices