Scraper APIs
Legacy product page
The per-site Scraper APIs (Amazon, Walmart, Google, Zillow, Idealista, and others) are deprecated. Every one of them ran on the same underlying request, which is now Fetch, paired with Extract for the sites it supports. Existing integrations keep working; new integrations should use Fetch directly.
Before this change, Zenrows offered a set of ready-made endpoints for popular sites, each returning structured data for that one target instead of raw HTML: Amazon, Walmart, Google Search, Zillow, Idealista, and others. Every endpoint shared the same request shape (pass a URL, get parsed fields back) and billed at the same per-request rate as the rest of the API.
01What it did
- One call per target page, returned as structured data instead of raw HTML.
- Handled JavaScript rendering and protected pages without extra configuration.
- No selectors or parsers to write or maintain per site.
- Fixed, predictable per-request pricing.
02Where each target lives today
The specific targets this page used to cover are now their own guides, built on Fetch: Amazon, Google, Zillow, and the rest of the scrape library. For any other site, Fetch works the same way without a dedicated guide.
03Frequently asked questions
What replaced the per-site endpoints?
Fetch, one request shape for any page. Pair it with Extract on the sites it supports for automatic structured output, or css_extractor for any other page.
Do existing per-site integrations still work?
Yes. Existing endpoints and integrations built on the old Scraper APIs are unaffected; this page just isn't where new integrations should start.