extract=auto to your Universal Scraper API call, and ZenRows identifies the meaningful data on the page and returns it as clean JSON, together with the raw HTML. There are no selectors to write, no schema to define, and no parser to maintain. The extraction adapts automatically when a website changes its layout.
Extract is currently in private beta and works on a curated set of domains. Any active ZenRows API key can use it on the enabled domains, with no extra setup needed. To get more domains enabled, contact ZenRows support.
How Extract works
Unlike general-purpose parsing rules that apply the same logic to every website, Extract builds and maintains an extraction that’s tailored to each individual site. ZenRows analyzes the pages on an enabled domain, identifies its meaningful data points, and keeps that extraction working as the site evolves, so you get richer and more complete fields than a one-size-fits-all approach can offer. During the private beta, this tailored extraction is only available for domains the ZenRows team has prepared and enabled. Coverage expands throughout the beta as more domains are onboarded.Basic usage
Enable Extract by adding theextract=auto parameter to your ZenRows request:
Response
A request withextract=auto returns Content-Type: application/json with two fields:
JSON
parsedcontains the structured data extracted from the page.htmlcontains the raw HTML of the scraped page. It’s included during the beta so you can validate the extracted data against the source.
parsed stays stable across requests for a given website, and new fields may be added over time as extraction improves, so treat unknown fields as additive rather than breaking. The html field is included for validation during the beta, and the overall response shape may evolve once the beta ends, so build your data pipeline around parsed and treat html as a validation aid rather than a permanent contract.
Coverage during the private beta
Extract is enabled per domain, not per account. The ZenRows team prepares and enables each domain, and once a domain is enabled, it works for every ZenRows API key, so there’s no customer allowlist to manage on your side. If you sendextract=auto for a domain that isn’t enabled yet, the request fails with a 402 error (AUTH010) explaining that the domain isn’t part of the beta. To get a domain enabled, contact ZenRows support and the team will onboard it.
Combining with other features
Extract works on the final HTML of the page, so it combines with the scraping features you already use. For JavaScript-heavy websites, add JavaScript Rendering with a short wait so dynamic content finishes loading before extraction. For protected websites, add Premium Proxy:When
extract=auto is set, it takes precedence over other output formats. autoparse, css_extractor, response_type, and outputs are ignored on that request.Extract vs. Autoparse vs. CSS Extractor
Pricing
Extract is free during the private beta. You only pay the standard Universal Scraper API cost of the underlying request, including JavaScript Rendering or Premium Proxy if you use them.Frequently Asked Questions (FAQ)
How is Extract different from Autoparse?
How is Extract different from Autoparse?
Autoparse (
autoparse=true) applies general-purpose extraction rules that work the same way on every website. Extract (extract=auto) builds an extraction tailored to each website, which returns richer, more complete fields and adjusts itself when the website’s layout changes. During the beta, Extract works only on enabled domains, while Autoparse remains available on any website.What happens on a domain that isn't enabled yet?
What happens on a domain that isn't enabled yet?
The request fails with a
402 error (AUTH010) stating that the domain isn’t enabled for the private beta. Contact ZenRows support to get additional domains onboarded, usually within a short time.Will the extracted fields change over time?
Will the extracted fields change over time?
The response shape for an enabled website stays stable. Your integration keeps receiving the same fields even as ZenRows improves extraction behind the scenes. New fields may be added over time, so treat unknown fields as additive rather than breaking.
Do I need to sign up separately to use Extract?
Do I need to sign up separately to use Extract?
No. Access is per domain, not per account. Any active ZenRows API key can use
extract=auto on a domain once that domain is enabled for the beta. There’s no separate signup or plan change required.Can I rely on the html field long term?
Can I rely on the html field long term?
Treat
html as a validation aid rather than a permanent part of the contract. It’s included during the beta so you can check the extracted data against the source page. Build your data pipeline around parsed, since the surrounding response shape may evolve once the beta ends.Can I combine Extract with other ZenRows features?
Can I combine Extract with other ZenRows features?
Yes. Extract works alongside JavaScript Rendering, Premium Proxy, and other request options. It takes precedence over other output formats, so
autoparse, css_extractor, response_type, and outputs are ignored on a request that sets extract=auto.