Map LayersGET/mapLayer

Realtor /mapLayer API

Stop scraping. Start building. The /mapLayer endpoint gives you instant, programmatic access to Realtor data through a clean, well-documented REST API that just works. No more wrestling with headless browsers, maintaining proxy pools, or writing fragile CSS selectors that break with every site redesign. RealtyAPI handles all of that behind a simple API key authentication, so your integration stays stable while we handle the complexity underneath. From early-stage prototype to scaled production system, this endpoint grows with your application — start with 250 free calls to validate your idea, then move to a paid plan when you are ready to ship.

What You Can Do With the /mapLayer Endpoint

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

Endpoint Parameters

Parameter	Type	Required	Description
`layer`	ENUM	Required	Which Realtor map-layer to fetch. Default: `Estimate`. Three families share this endpoint — the response shape is determined by the layer you pick: TopHap vector layers (return cell arrays with `lat`/`lng` + per-layer attributes): - `Estimate` — RealEstimate℠ valuation per hex cell - `EstimatePpsqft` — Valuation $/sqft per cell - `LotAcres` — Lot size in acres - `LotSlope` — Lot slope % - `Sqft` — Home size (sqft) - `YearBuilt` — Year built - `Noise` — Noise score - `MarketHotness` — RDC Hotness Score per ZIP (also returns a `us_hotness_score_label`) - `SoldPriceVsListPrice` — Sold-vs-list % over the last 365d - `SoldSqft` — Sold $/sqft over the last 365d - `DaysOnMarket` — Median Days On Market over the last 365d - `HousingForecast` — RDC 12-month forecast % change per ZIP - `Neighborhoods` — Neighborhood centroids + IDs (`slug_id`, `geo_id`, `neighborhood`) Raster layers (return base64 PNG tiles in `data.tiles[]`): - `Flood` — First Street® flood-risk overlay - `Wildfire` — First Street® wildfire-risk overlay - `Heat` — Max-temperature overlay (hottest month °F) - `Wind` — Wind-risk overlay - `Air` — Air-quality (bad-air days) overlay GraphQL records: - `Schools` — All schools + districts inside the region's bbox. Values: `Estimate, EstimatePpsqft, LotAcres, LotSlope, Sqft, YearBuilt, Noise, MarketHotness, SoldPriceVsListPrice, SoldSqft, DaysOnMarket, HousingForecast, Flood, Wildfire, Heat, Wind, Air, Schools, Neighborhoods`
`location`	STRING	Required	Region to fetch the map layer for. Accepts anything Realtor.com's autocomplete handles — ZIP, city, neighborhood, county, state, or full address. - Example 1: `10027` (ZIP) - Example 2: `New York, NY` (city) - Example 3: `Harlem, New York, NY` (neighborhood) - Example 4: `9504 Quail Village Ln, Austin, TX 78758` (address) The input is resolved internally to a centroid + bbox; tiles are fetched around that centroid at the requested `zoom`.
`zoom`	NUMBER	Optional	Web-Mercator tile zoom level for the fetched tiles. Typical range `10–16`. Leave blank to use the per-layer default: - TopHap hex-cell layers (Estimate, Sqft, Noise, etc.): `12` - TopHap per-ZIP layers (MarketHotness, HousingForecast): `9` - Neighborhoods / Schools: `12` - Raster layers (Flood, Wildfire, Heat, Wind, Air): `11` - Parcel-resolution data (per-property): set zoom to `16` and the endpoint switches to the parcel tile source.
`relativeYear`	NUMBER	Optional	Forecast horizon for raster layers only (Flood, Wildfire, Heat, Wind, Air). Accepted values: `0` (current year, default), `15`, `30`. Ignored for non-raster layers — there's no time dimension on TopHap vector cells.

Required Parameters

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

JSON Response

Receive structured JSON containing /maplayer data from Realtor. Parse it directly into your application models.

Real-Time Results

Every request fetches live Realtor 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 /mapLayer endpoint in seconds.

Python

import requests

url = "https://realtor.realtyapi.io/mapLayer"

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

params = {
    "layer": "Estimate,EstimatePpsqft,LotAcres,LotSlope,Sqft,YearBuilt,Noise,MarketHotness,SoldPriceVsListPrice,SoldSqft,DaysOnMarket,HousingForecast,Flood,Wildfire,Heat,Wind,Air,Schools,Neighborhoods",
    "location": "10027"
}

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

Why Choose RealtyAPI's /mapLayer Endpoint

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

Real-Time Data Access

Get the most current /maplayer data from Realtor 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 /maplayer data through this carefully designed endpoint.

/mapLayer Endpoint Use Cases

Real-world applications that leverage the /mapLayer endpoint for Realtor data.

Data Analysis

Analyze /maplayer data from Realtor to gain insights and make data-driven decisions about real estate markets.

Market Monitoring

Monitor Realtor /maplayer data to track changes, pricing trends, and market movements in real time.

Application Integration

Integrate /maplayer data from Realtor into your web applications, mobile apps, or internal tools.

Workflow Automation

Automate data collection and processing workflows using Realtor /maplayer data to improve team efficiency.

Reporting & Analytics

Generate reports and dashboards using Realtor /maplayer data for stakeholders, investors, or clients.

Custom Solutions

Build custom real estate solutions that leverage Realtor /maplayer data for your specific business needs.

Frequently Asked Questions

Common questions about the /mapLayer endpoint.

Is the /mapLayer endpoint official?

No, RealtyAPI provides an unofficial /mapLayer endpoint that lets you access Realtor 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 /maplayer data from Realtor. 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 Realtor Endpoints

GET/details/byaddress GET/details/byid GET/details/byurl GET/autocomplete GET/search/bylocation GET/search/byzip GET/search/bycoordinates GET/search/bypolygon GET/search/byurl GET/agent GET/mortgage

Ready to Integrate the /mapLayer Endpoint?

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

Common Terms for /mapLayer Endpoint Access

Realtor /mapLayer API integration/mapLayer data APIAccess /maplayer data programmaticallyRealtor /mapLayer API for developers/mapLayer API endpoint/mapLayer API documentationHow to use Realtor /mapLayer APIRealtor /mapLayer API wrapper/mapLayer real estate dataRealtor /mapLayer REST API