Extract works on any prepared domain, and you can prepare a new one yourself. The one exception is a site Extract is not enabled for; see domain coverage. Any active Zenrows API key can use it, with no extra setup needed.
extract=auto to your Fetch 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, and the extraction adapts automatically when a website changes its layout.
How It 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 a domain’s pages, 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.Basic Usage
Enable Extract by adding theextract=auto parameter to your Zenrows request:
cURL
Content-Type: application/json with a parsed field containing the structured data, and an html field with the raw page so you can validate the result against the source.
Two optional parameters shape what comes back: extract_fields narrows parsed to the fields you name, and extract=standard swaps each website’s own field names for a canonical schema shared across a vertical, on the API and currently for real estate only.
OpenAPI Spec
Theextract parameter, including its modes, and extract_fields are part of the Fetch endpoint’s definition in the Zenrows OpenAPI 3.1 spec at www.zenrows.com/openapi.json, which is listed in the RFC 9727 API catalog at www.zenrows.com/.well-known/api-catalog.
The spec doesn’t describe the Extract endpoints under /v1/extract/ yet. Use the Extract reference pages for those.
Next Steps
Extract Reference
Full parameter reference: response shape, domain coverage, pricing, and FAQ.
Autoparse (Legacy)
The deprecated general-purpose parser, and how to migrate an integration off it.