Get Regional ZHVI, ZORI, Sales and Inventory Data

View all Zillow Real Estate Data API endpoints →

Provide location text or a region_id; at least one is needed for an intentional region request even though both fields are individually optional in the schema. Use autocomplete to review available region types, and keep selected request geography separate from response-confirmed geography. Behavior when both inputs are supplied was not verified. The observed Seattle response contained success:true and data.region, home_values, rentals, sales, listings and neighbors, plus meta. home_values included zhvi, zhvi_yoy, zhvi_date, zhvi_history and an empty forecast array. rentals included zori, zori_date, zori_history, national_zori and national_zori_history. The two regional index histories each had 100 date/value/change_pct records. sales included median_sale_price, median_sale_price_date, median_sale_to_list, pct_sold_above_list, pct_sold_below_list and sales_history. listings included median_list_price, new_listings, for_sale_inventory, median_days_to_pending, listings_date and listings_history. Nine neighbors supplied region_id, name, zhvi and relative url fields. Counts and historical coverage can change. Every field in data.region was null despite populated analytics. Retain the requested city or selected region ID as request provenance, not a verified response label; sending region_id has not been demonstrated to fix the null block. ZHVI and ZORI were dated 2026-09-30, while median sale price was dated 2026-08-31. Store reporting dates per metric rather than assigning the retrieval date or one shared month to all values. ZHVI is not median sale price, ZORI is not an individual home’s rent and a regional snapshot is not a property appraisal.

API Features

Distinct home-value and rent indices Read home_values.zhvi and rentals.zori with their own histories rather than confuse them with asking prices or a particular home’s rent.
Metric-specific reporting periods Keep zhvi_date, zori_date, median_sale_price_date and listings_date attached to their measurements; the observed sales month differed from the indices.
Explicit missing region identity Preserve null fields inside data.region and record the requested location separately without inventing a confirmed region label.
Sales, inventory and neighbor context Research reported sales ratios, listing metrics and named neighboring regions alongside the index series, retaining their coverage limits.

Live API Demo

GET /api/project/zillow-real-estate/get-market-analytics

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/zillow-real-estate/get-market-analytics?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Why can populated market analytics have an empty region block?

That was observed for Seattle: every data.region field was null although indices, sales and inventory were populated. Preserve the requested geography as provenance, do not invent returned identity and do not claim region_id repairs it.

Are ZHVI, ZORI, median sale price and asking price equivalent?

No. ZHVI is a regional home-value measure, ZORI a regional rent measure, median_sale_price a sales measure and median_list_price a listing measure. None is a valuation or rent promise for a particular home.

Can I label the whole response with the most recent date?

No. The observed index records were dated 2026-09-30 while median sale price was dated 2026-08-31. Preserve each metric’s own reporting date; retrieval time is a separate observation.

Related operations

Guides

View Subscription Plans →