Search ZillowGET/search/bypolygon

Zillow /search/bypolygon API

The /search/bypolygon endpoint opens up Zillow data for your real estate applications, giving you programmatic access to information that would otherwise require manual research or unreliable scraping. Whether you are building a property search tool, an investment analysis platform, a rental comparison engine, or a market analytics dashboard, this endpoint delivers structured, reliable data on demand. Every response is normalized into a consistent JSON schema, so you don't need to write different parsers for different data sources. Combined with RealtyAPI's other endpoints, you can build a complete real estate data layer that spans multiple providers through a single integration.

What You Can Do With the /search/bypolygon Endpoint

Here's what this endpoint provides and how you can use the data it returns.

Endpoint Parameters

Parameter	Type	Required	Description
`polygon`	STRING	Required	Enter polygon ordinates:
`page`	NUMBER	Optional	Zillow provides `1000` results on each search. This endpoint returns `200` results per call. So the maximum page number could be `5`. - `To collect all the data`: Narrow down your search into smaller areas. (Search by zip code, Set different listPriceRange, try different homeTypes)
`sortOrder`	ENUM	Optional	Select how you want to sort your search results. - Defaults: - For Sale : `Homes_for_you` - For Rent : `Rental_Priority_Score` - Sold : `Newest` Values: `Homes_for_you, Rental_Priority_Score, Price_High_to_Low, Price_Low_to_High, Newest, Bedrooms, Bathrooms, Square_Feet, Lot_Size, Year_Built`
`listingStatus`	ENUM	Required	Select which type of property data you want to find. Values: `For_Sale, For_Rent, Sold`
`listPriceRange`	STRING	Optional	Possible Inputs: - For Minimum Price: `min:5000` - For Maximum Price: `max:500000` - For a Price Range: `min:5000, max:500000`
`monthlyPayment`	STRING	Optional	Only used for listingStatus: `For_Sale`. Possible Inputs: - For Minimum Payment: `min:5000` - For Maximum Payment: `max:50000` - For a Payment Range: `min:5000, max:50000`
`downPayment`	NUMBER	Optional	Only used for listingStatus: `For_Sale`. Input a down payment (dollars). Example: `15000`. For No Down Payment, do not input anything.
`bed_min`	ENUM	Optional	Input the minimum number of bedrooms that should be present on the listings. For an exact match, use bed_min and bed_max equal. For example, to see properties with 3 bedrooms: `bed_min=3, bed_max=3` Values: `No_Min, Studio, 1, 2, 3, 4, 5`
`bed_max`	ENUM	Optional	Input the maximum number of bedrooms that could be present on the listings. Values: `No_Max, Studio, 1, 2, 3, 4, 5`
`bathrooms`	ENUM	Optional	Input Mapping Explanation: `Any` → Any `OnePlus` → 1+ `OneHalfPlus` → 1.5+ `TwoPlus` → 2+ `ThreePlus` → 3+ `FourPlus` → 4+ Values: `Any, OnePlus, OneHalfPlus, TwoPlus, ThreePlus, FourPlus`
`homeType`	STRING	Optional	For multiple inputs, separate them with a comma or keep it empty for all types selected. 1. Possible values when `listingStatus` = `For_Rent`: - `Houses, Apartments/Condos/Co-ops, Townhomes` 2. Possible values when `listingStatus` = `For_Sale` or `Sold`: - `Houses, Townhomes, Multi-family, Condos/Co-ops, Lots-Land, Apartments, Manufactured`
`space`	STRING	Optional	For multiple inputs, separate them with a comma. Keeping it empty will `NOT` select any types. - Only used for `listingStatus` = `For_Rent` - Possible values: `Entire Place, Room`
`maxHOA`	ENUM	Optional	Only used for listingStatus: `For_Sale` or `Sold`. Values: `Any, No_HOA_Fee, 50_dollars_month, 100_dollars_month, 200_dollars_month, 300_dollars_month, 400_dollars_month, 500_dollars_month, 600_dollars_month, 700_dollars_month, 800_dollars_month, 900_dollars_month, 1000_dollars_month`
`incIncompleteHOA`	BOOLEAN	Optional	Include homes with incomplete HOA data. Only used for listingStatus: `For_Sale` or `Sold`.
`listingType`	ENUM	Optional	Only used for listingStatus: `For_Sale`. Default: By_Agent Values: `By_Agent, By_Owner_and_Other`
`listingTypeOptions`	STRING	Optional	Only used for listingStatus: `For_Sale`. For multiple inputs, separate them with a comma or keep it empty for all types selected. 1. Possible values when `listingType` = `By_Agent`: - `Agent listed, New Construction, Fore-closures, Auctions, Foreclosed, Pre-foreclosures` 2. Possible values when `listingType` = `By_Owner_and_Other`: - `Owner Posted, Agent listed, New Construction, Fore-closures, Auctions, Foreclosed, Pre-foreclosures`
`propertyStatus`	STRING	Optional	For multiple inputs, separate them with a comma. Keeping it empty will NOT select any types. - Only used for `listingStatus` = `For_Sale` - Possible values: `Coming soon, Accepting backup offers, Pending & under contract`
`tours`	STRING	Optional	For multiple inputs, separate them with a comma. Keeping it empty will NOT select any types. 1. Possible values when `listingStatus` = `For_Rent`: - `Must have 3D Tour` 2. Possible values when `listingStatus` = `For_Sale`: - `Must have open house, Must have 3D Tour`
`parkingSpots`	ENUM	Optional	- Only used for `listingStatus` = `For_Sale` or `Sold` - Where: `Any` → Any `OnePlus` → 1+ `TwoPlus` → 2+ `ThreePlus` → 3+ `FourPlus` → 4+ Values: `Any, OnePlus, TwoPlus, ThreePlus, FourPlus`
`haveGarage`	BOOLEAN	Optional	- Only used for `listingStatus` = `For_Sale` or `Sold`
`move_in_date`	STRING	Optional	Only used for `listingStatus` = `For_Rent`
`hideNoDateListings`	BOOLEAN	Optional	Hide listings with no move-in date provided. Only used: `For_Rent`
`squareFeetRange`	STRING	Optional	Possible Inputs: - For Minimum Square Feet: `min:500` - For Maximum Square Feet: `max:5000` - For a Square Feet Range: `min:500, max:5000`
`lotSizeRange`	STRING	Optional	Values should be in square feet. For acre-sqft calculation: `1 acre` = `43560 sqft` 1. Possible Inputs: - For Minimum Lot Size: `min:1000` - For Maximum Lot Size: `max:7500` - For a Lot Size Range: `min:1000, max:7500`
`yearBuiltRange`	STRING	Optional	Possible Inputs: - For Minimum Year Built: `min:2011` - For Maximum Year Built: `max:2024` - For a Year Built Range: `min:2011, max:2024`
`mustHaveBasement`	ENUM	Optional	— Values: `No, Yes_Finished, Yes_Unfinished, Yes_Both`
`singleStoryOnly`	BOOLEAN	Optional	—
`hide55plusComm`	BOOLEAN	Optional	Senior Living: Hide 55+ communities - Only used for `listingStatus` = `For_Sale` or `Sold`
`pets`	STRING	Optional	For multiple inputs, separate them with a comma. - Only used for `listingStatus` = `For_Rent` - Possible values: `Allow large dogs, Allow small dogs, Allow cats`
`soldInLast`	ENUM	Optional	- Only used for `listingStatus` = `Sold` Values: `Any, 1_day, 7_days, 14_days, 30_days, 90_days, 6_months, 12_months, 24_months, 36_months`
`otherAmenities`	STRING	Optional	For multiple inputs, separate them with a comma. Keeping it empty will NOT select any types. 1. Possible values when `listingStatus` = `For_Sale` or `Sold`: - `Must have A/C, Must have pool, Waterfront` 2. Possible values when `listingStatus` = `For_Rent`: - `Must have A/C, Must have pool, Waterfront, On-site Parking, In-unit Laundry, Accepts Zillow Applications, Income Restricted, Apartment Community`
`view`	STRING	Optional	For multiple inputs, separate them with a comma. Keeping it empty will NOT select any types. - Possible values: `City, Mountain, Park, Water`
`daysOnZillow`	ENUM	Optional	- Only used for `listingStatus` = `For_Sale` or `Rent` Values: `Any, 1_day, 7_days, 14_days, 30_days, 90_days, 6_months, 12_months, 24_months, 36_months`
`keywords`	STRING	Optional	MLS #, yard, fireplace, horses, etc

Required Parameters

This endpoint requires polygon, listingStatus to fetch data. Pass these as query parameters in your request.

JSON Response

Receive structured JSON containing /search/bypolygon data from Zillow. Parse it directly into your application models.

Real-Time Results

Every request fetches live Zillow data. No stale caches — you always get the most current information available.

Error Handling

Clear HTTP status codes and error messages help you handle edge cases gracefully. See our documentation for the full error reference.

Quick Start Example

Make your first request to the /search/bypolygon endpoint in seconds.

Python

import requests

url = "https://zillow.realtyapi.io/search/bypolygon"

headers = {
    "x-realtyapi-key": "YOUR_API_KEY"
}

params = {
    "polygon": "40.855234480429694 -74.17845832952554, 40.855234480429694 -74.19555443455033, 40.839398873832685 -74.24344650496268, 40.80972482702799 -74.28449657022708, 40.78908363119005 -74.296929020874, 40.77047722402841 -74.29867566132631, 40.758686571326656 -74.29488731066652, 40.74457283221658 -74.27932595196283, 40.7208001408447 -74.24336135180303, 40.69433436537408 -74.17940690332038, 40.68872311180734 -74.15785903804887, 40.68534441906408 -74.11065612092496, 40.688994903106064 -74.08725269587569, 40.6996418749718 -74.06332250180179, 40.736494491243455 -74.01404222522173, 40.75810156036361 -73.99800162982523, 40.780478366299285 -73.9884228226182, 40.81917604658057 -73.98606029895414, 40.835810580257295 -73.99136755778092, 40.85944179559576 -74.01440264299832, 40.867487214707964 -74.02566670962027, 40.875048003689685 -74.04705615165555, 40.87701705179268 -74.08824087399046, 40.870109405210556 -74.12233010923437, 40.84829460307693 -74.15796597388221, 40.85470124757849 -74.17896529341184",
    "listingStatus": "For_Sale,For_Rent,Sold"
}

response = requests.get(url, headers=headers, params=params)
data = response.json()
print(data)

Why Choose RealtyAPI's /search/bypolygon Endpoint

Built for developers who need reliable real estate data without the infrastructure overhead.

Real-Time Data Access

Get the most current /search/bypolygon data from Zillow without dealing with rate limits or IP blocks.

Simple Integration

Clear documentation and straightforward REST design make it easy to integrate this endpoint into any tech stack.

High Reliability

Our infrastructure ensures high uptime and consistent performance for your production applications.

Comprehensive Data

Access detailed /search/bypolygon data through this carefully designed endpoint.

/search/bypolygon Endpoint Use Cases

Real-world applications that leverage the /search/bypolygon endpoint for Zillow data.

Data Analysis

Analyze /search/bypolygon data from Zillow to gain insights and make data-driven decisions about real estate markets.

Market Monitoring

Monitor Zillow /search/bypolygon data to track changes, pricing trends, and market movements in real time.

Application Integration

Integrate /search/bypolygon data from Zillow into your web applications, mobile apps, or internal tools.

Workflow Automation

Automate data collection and processing workflows using Zillow /search/bypolygon data to improve team efficiency.

Reporting & Analytics

Generate reports and dashboards using Zillow /search/bypolygon data for stakeholders, investors, or clients.

Custom Solutions

Build custom real estate solutions that leverage Zillow /search/bypolygon data for your specific business needs.

Frequently Asked Questions

Common questions about the /search/bypolygon endpoint.

Is the /search/bypolygon endpoint official?

No, RealtyAPI provides an unofficial /search/bypolygon endpoint that lets you access Zillow data through our platform. We handle the complexities of data collection so you can focus on building your application.

How current is the data?

We provide real-time /search/bypolygon data from Zillow. When you make a request, we fetch the latest information available.

Can I use this endpoint in production?

Absolutely. Many businesses rely on RealtyAPI's endpoints for their production applications. Our infrastructure is designed for reliability and performance.

What happens if I exceed my API limit?

On paid plans, you can enable overage billing so your application keeps working. Free plan users can upgrade at any time to increase their quota.

Is there rate limiting?

Rate limits vary by plan. Free tier allows up to 10 requests per second. Paid plans offer higher limits suitable for production workloads.

What programming languages are supported?

RealtyAPI is a standard REST API, so it works with any language that can make HTTP requests: Python, JavaScript, Go, PHP, Ruby, Java, C#, and more.

Other Zillow Endpoints

GETBy Property Address GETBy Zillow URL GETBy Zpid GET/By Property Address GET/By Zpid GET/By Zillow URL GET/search/byaddress GET/search/byurl GET/search/bymapbounds GET/search/bycoordinates GET/search/bymls GET/search/by-ai-prompt GET/autocomplete GET/ Listing Price GET/ Rent Zestimate History GET/ Tax Assessment History GET/ Tax Paid History GET/ Zestimate History (Home Values)GET/ Zestimate Percent Change GET/ similar_properties GET/ climate GET/ comparable_homes GET/ nearby_properties GET/ owner-agent (listedby_info)GET/ pricehistory GET/ property_images GET/ taxinfo_history GET/ walk_transit_bike GET/ lotid_from_address GET/ apartment_details GET/ housing_market (zhvi)GET/ rental_market_trends GET/agent/search GET/agent/details GET/agent/forSaleProperties GET/agent/forRentProperties GET/agent/soldProperties GET/agent/reviews GET/ skip_trace/byaddress GET/ skip_trace/details_by_id GET/api limit check GET/check status GET/custom_a/byaddress GET/custom_ab/byaddress GET/custom_ac/byzpid GET/custom_ad/byzpid GET/custom_ad/searchByAddress GET/custom_ad/searchByCoordinates GET/custom_ad/searchByPolygon GET/custom_ae/searchByAddress GET/custom_ag/byzpid GET/image mask

Ready to Integrate the /search/bypolygon Endpoint?

Get started with 250 free API calls. No credit card required.

Common Terms for /search/bypolygon Endpoint Access

Zillow /search/bypolygon API integration/search/bypolygon data APIAccess /search/bypolygon data programmaticallyZillow /search/bypolygon API for developers/search/bypolygon API endpoint/search/bypolygon API documentationHow to use Zillow /search/bypolygon APIZillow /search/bypolygon API wrapper/search/bypolygon real estate dataZillow /search/bypolygon REST API