Realestate.com.au API
Search Realestate.com.au

GET/search/bypolygon

Realestate.com.au /search/bypolygon API

The /search/bypolygon endpoint opens up Realestate.com.au 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.

99.9% Uptime
|Real-Time Data|JSON Output

quick-start.py

import requests

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

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

params = {
    "polygon": "151.26 -33.90,151.28 -33.90,151.28 -33.88,151.26 -33.88"
}

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

200 OK·application/json

Endpoint Reference

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

23 params

Parameter	Type	Required	Description
`polygon`	STRING	Required	Polygon ring as `lon lat,lon lat,...` (longitude first, then latitude — GeoJSON convention; whitespace between lon and lat, comma between points). Note: realestate.com.au's `geoShapeSearch` field accepts arbitrary polygons syntactically but does not actually filter by them — only `boundingBoxSearch` narrows results, so we collapse the polygon to its axis-aligned bounding box internally. The endpoint stays available so callers don't have to do the bbox math themselves. Example (a small box around Bondi, Sydney): `151.26 -33.90,151.28 -33.90,151.28 -33.88,151.26 -33.88`
`page`	NUMBER	Optional	1-based page number. The response includes a `nextPage` boolean — keep paging until `nextPage = false`.
`resultCount`	NUMBER	Optional	Results per page. - Default: `30` - Min: `1` - Max: `200`
`sortOrder`	ENUM	Optional	Sort order for the result list. Default: `Recommended`. - `Recommended` — realestate.com.au's default relevance bucket - `Newest` — most recently listed first - `Oldest` — least recently listed first - `Price_Low_to_High` - `Price_High_to_Low` - `Most_Recently_Sold` — only meaningful with `searchType` = `Sold` - `Oldest_Sold` — only meaningful with `searchType` = `Sold` Values: `Recommended, Newest, Oldest, Price_Low_to_High, Price_High_to_Low, Most_Recently_Sold, Oldest_Sold`
`searchType`	ENUM	Optional	Listing status. Default: `For_Sale`. - `For_Sale` — Buy channel - `For_Rent` — Rent channel - `Sold` — Sold history (use `maxSoldAge` to bound the window) Values: `For_Sale, For_Rent, Sold`
`propertyType`	STRING	Optional	Comma-separated property types. Leave empty to include all. Allowed values: `House, Apartment, Unit, Townhouse, Villa, Land, Acreage, Rural, Block_of_Units, Retirement` Aliases accepted: `Apartment&Unit` → Apartment + Unit; `Townhomes` → Townhouse.
`priceRange`	STRING	Optional	Price range, in AUD. Possible Inputs: - For Minimum Price: `min:500000` - For Maximum Price: `max:1500000` - For a Price Range: `min:500000,max:1500000`
`bedsRange`	STRING	Optional	Bedroom range. Studio = `min:0`. realestate.com.au caps the wire vocabulary at 5+ — values above 5 are mapped to `5+`. Possible Inputs: - For Minimum Beds: `min:3` - For Maximum Beds: `max:5` - For an Exact Match: `min:3,max:3` - For a Range: `min:3,max:5`
`bathsRange`	STRING	Optional	Bathroom range — only `min` is honored by realestate.com.au's search API; `max` is ignored. Possible Inputs: - For Minimum Baths: `min:2` - (`max:3` would be ignored)
`carSpacesRange`	STRING	Optional	Car-space range — only `min` is honored by realestate.com.au's search API; `max` is ignored. Possible Inputs: - For Minimum Car Spaces: `min:1`
`landSizeRange`	STRING	Optional	Land area range, in square metres (sqm). Possible Inputs: - For Minimum Land Size: `min:500` - For Maximum Land Size: `max:5000` - For a Range: `min:500,max:5000`
`surroundingSuburbs`	BOOLEAN	Optional	Set to `true` to include listings from neighboring suburbs around the search location, or `false` to restrict strictly to the named suburb. Default: `true` (matches the realestate.com.au website default).
`excludeUnderContract`	BOOLEAN	Optional	Set to `true` to exclude listings currently under contract.
`excludeAuctions`	BOOLEAN	Optional	Set to `true` to exclude auction listings.
`excludePrivateSales`	BOOLEAN	Optional	Set to `true` to exclude private-sale listings.
`excludeNoDisplayPrice`	BOOLEAN	Optional	Set to `true` to exclude listings that don't show a display price (e.g. `Contact Agent`, `Offers above`).
`excludeDepositTaken`	BOOLEAN	Optional	Set to `true` to exclude listings that already have a deposit taken (rentals only).
`newListingOnly`	BOOLEAN	Optional	Set to `true` to return only listings added in the last few days (realestate.com.au's `New` filter).
`furnished`	BOOLEAN	Optional	Set to `true` to return only furnished listings. Used for `searchType` = `For_Rent`.
`petsAllowed`	BOOLEAN	Optional	Set to `true` to return only pet-allowed listings. Used for `searchType` = `For_Rent`.
`constructionStatus`	ENUM	Optional	Construction status filter. Leave empty to include both. - `established` — existing-home listings only - `new` — new-construction listings only Values: `established, new`
`keywords`	STRING	Optional	Free-text amenity keywords matched against listing descriptions, comma-separated. Examples: `pool`, `garage`, `pool,garage`
`maxSoldAge`	STRING	Optional	Bound the recency window for sold history. Format: `value:unit` where unit is one of `days`, `months`, `years`. Only meaningful with `searchType` = `Sold`. Examples: `90:days`, `6:months`, `2:years`

Required Parameters

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

JSON Response

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

Real-Time Results

Every request fetches live Realestate.com.au 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.

What You Can Build

/search/bypolygon Endpoint Use Cases.

Real-world applications that leverage the /search/bypolygon endpoint for Realestate.com.au data.

Data Analysis

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

Market Monitoring

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

Application Integration

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

Workflow Automation

Automate data collection and processing workflows using Realestate.com.au /search/bypolygon data to improve team efficiency.

Reporting & Analytics

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

Custom Solutions

Build custom real estate solutions that leverage Realestate.com.au /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 Realestate.com.au 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 Realestate.com.au. 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 Realestate.com.au Endpoints

GET/details/byid GET/details/byurl GET/details/byaddress GET/autocomplete GET/search/bylocation GET/search/byzip GET/search/bycoordinates GET/search/byurl

No credit card required

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

Realestate.com.au /search/bypolygon API integration/search/bypolygon data APIAccess /search/bypolygon data programmaticallyRealestate.com.au /search/bypolygon API for developers/search/bypolygon API endpoint/search/bypolygon API documentationHow to use Realestate.com.au /search/bypolygon APIRealestate.com.au /search/bypolygon API wrapper/search/bypolygon real estate dataRealestate.com.au /search/bypolygon REST API

Realestate.com.au /search/bypolygon API

What You Can Do With
the /search/bypolygon Endpoint.

Endpoint Parameters

Required Parameters

JSON Response

Real-Time Results

Error Handling

Why Choose RealtyAPI's
/search/bypolygon Endpoint.

Real-Time Data Access

Simple Integration

High Reliability

Comprehensive Data

/search/bypolygon Endpoint Use Cases.

Data Analysis

Market Monitoring

Application Integration

Workflow Automation

Reporting & Analytics

Custom Solutions

Frequently Asked Questions

Other Realestate.com.au Endpoints

Ready to integrate the
/search/bypolygon endpoint?

Common Terms for /search/bypolygon Endpoint Access

Realestate.com.au /search/bypolygon API

What You Can Do Withthe /search/bypolygon Endpoint.

Endpoint Parameters

Required Parameters

JSON Response

Real-Time Results

Error Handling

Why Choose RealtyAPI's/search/bypolygon Endpoint.

Real-Time Data Access

Simple Integration

High Reliability

Comprehensive Data

/search/bypolygon Endpoint Use Cases.

Data Analysis

Market Monitoring

Application Integration

Workflow Automation

Reporting & Analytics

Custom Solutions

Frequently Asked Questions

Other Realestate.com.au Endpoints

Ready to integrate the/search/bypolygon endpoint?

Common Terms for /search/bypolygon Endpoint Access

What You Can Do With
the /search/bypolygon Endpoint.

Why Choose RealtyAPI's
/search/bypolygon Endpoint.

Ready to integrate the
/search/bypolygon endpoint?