Realtor API endpoints
Explore 12 endpoints for accessing Realtor real estate data. Each endpoint is designed for a specific use case and returns structured JSON.
/details/byaddressINPUT: Property Address (`9504 Quail Village Ln, Austin, TX 78758`) Get **full property details** by a Realtor.com street address. The API resolves the address to a `property_id` internally — split into street line + city/state/zip — and disambiguates by city/state/zip when multiple matches come back. ##### Note: - This endpoint costs `2 credits/call` and is slightly slower than `/details_byid`. - If you already know the `property_id` (from any `/search_*` response or from a Realtor.com listing URL), use the [/details_byid endpoint](https://realtyapi.io/dashboard?tab=playground&api=realtor&endpoint=detailsbyid) — it is `1 credit/call` and ~2× faster.
/details/byidINPUT: `property_id` (e.g. `8955838462`) Get **full property details** using Realtor.com's internal `property_id`. The fastest details endpoint — `1 credit/call`. ##### Where to find a property_id: - Returned in every `/search_*` response (each result includes `property_id` and `listing_id`). - Embedded in a Realtor.com listing URL: the trailing `_M<digits>-<digits>` chunk is the `property_id` (hyphens are display separators, strip them). - Example URL: `https://www.realtor.com/realestateandhomes-detail/9504-Quail-Village-Ln_Austin_TX_78758_M89558-38462` - `M89558-38462` → `property_id = 8955838462` If you only have an address, use [/details_byaddress](https://realtyapi.io/dashboard?tab=playground&api=realtor&endpoint=detailsbyaddress) instead.
/details/byurlINPUT: Realtor.com listing URL Get **full property details** from a Realtor.com listing URL. The trailing `_M<digits>-<digits>` chunk is parsed to extract the `property_id`. If the URL has no `_M` segment, the address slug is treated as a free-text address and resolved via the search index. ##### Supported URL shapes: - `https://www.realtor.com/realestateandhomes-detail/<address-slug>_M<property_id>` ✅ fastest - `https://www.realtor.com/realestateandhomes-detail/<address-slug>_<city>_<ST>_<zip>_M<property_id>-<listing_id>` ✅ fastest - `https://www.realtor.com/realestateandhomes-detail/<address-slug>` ✅ falls back to address resolution
/autocompleteRealtor.com **search-box autocomplete** (`/parser/suggest`). Returns ranked suggestions across cities, ZIPs, neighborhoods, counties, addresses, schools, school districts, parks, universities and streets — each with geo metadata (`centroid`, `slug_id`, `geo_id`, `state_code`, etc.) ready to feed into a `/search_*` call.
/search/bylocationSearch Realtor.com listings by **free-text location** — city, ZIP, neighborhood, county, or state. Returns paginated listings with `property_id`, `listing_id`, address, photos, price, beds/baths/sqft, status, days on market, listing date, and the listing-advertiser block (use `fulfillment_id` with [/agent](https://realtyapi.io/dashboard?tab=playground&api=realtor&endpoint=agent)). Supports the **full filter set** below (status, price/beds/baths ranges, property types, new-construction toggle, open-house, tours, pets, keywords, sort, pagination).
/search/byzipSearch Realtor.com listings by **US ZIP code**. Cleaner than `/search_bylocation` when you specifically want a postal-code search (no fuzzy matching). Supports the **full filter set** below.
/search/bycoordinatesSearch Realtor.com listings inside a **circular area** defined by `latitude` + `longitude` + `radius` (miles). The circle is converted internally to an axis-aligned bounding-box polygon (4-corner ring). For arbitrary shapes use [/search_bypolygon](https://realtyapi.io/dashboard?tab=playground&api=realtor&endpoint=searchbypolygon). Supports the **full filter set** below.
/search/bypolygonSearch Realtor.com listings inside an **arbitrary polygon**. Useful for irregular boundaries — neighborhoods, school catchment areas, drawn map regions. The polygon is sent to Realtor.com as a GeoJSON `Polygon` boundary. **Polygon format**: a comma-separated list of `lon lat` pairs (note: longitude first, then latitude — GeoJSON convention). The ring will be auto-closed if the first/last vertex differ. Supports the **full filter set** below.
/search/byurlRun the search that a Realtor.com **search URL** represents. The location slug + filter segments (`price-`, `beds-`, `baths-`, `sqft-`, `lot-sqft-`, `type-`, `shw-nc`, `nc-hide`, `shw-oh`, `show-price-reduced`, `shw-pr`) are parsed into the friendly query-builder vocabulary, then routed through the matching `/search_by*` endpoint (postal / city / neighborhood) under the hood. Additional query-string filters you pass alongside `url` will be **layered on top** of whatever the URL encodes (filters from extra params override the URL's parsed filters).
/agentGet **Realtor.com agent branding** by `fulfillment_id`. Returns the agent's full name, brokerage / office, ratings & review count, listing stats, avatar URL + initials, and Realtor.com profile URL — everything you need to build a "Listed by" widget on a property page. ##### Where to find a fulfillment_id: Every `/details_*` and `/search_*` response includes a `listing_advertiser` block (or per-listing `advertisers[]`) with the seller / agent's `fulfillment_id`. Pass it here.
/mortgageEstimate the **monthly mortgage payment** for a home price using Realtor.com's mortgage calculator. Returns: - `loan_amount` — price minus down payment - `monthly_payment` — total $/mo - `total_payment` — total over the loan term - `breakdown` — per-component split: principal & interest, property tax, home insurance, HOA, mortgage insurance Useful for affordability widgets, listing detail pages, and matching the ["Monthly payment" filter](https://realtyapi.io/dashboard?tab=playground&api=realtor&endpoint=searchbylocation) on Realtor.com searches.
/mapLayerReturns Realtor.com map-overlay data for any region. Pick one of 19 layers (Estimate, MarketHotness, Schools, Flood, etc.) via the `layer` enum and pass a free-text `location` (zip / city / neighborhood / address). Response shape varies by layer family — vector cells, base64 PNG tiles, or GraphQL records — and always echoes the resolved bbox + center so you can render the overlay on your own map.
We built RealtyAPI so developers can focus on their products, not on data collection infrastructure.
Get the most current Realtor data without dealing with rate limits, IP blocks, or anti-bot protections. Our infrastructure handles the heavy lifting.
Clear documentation and a straightforward REST API make it easy to start pulling Realtor data into your application within minutes.
Our infrastructure is built for uptime and performance. Rely on consistent, uninterrupted access to Realtor data for your production applications.
Access a wide range of Realtor data points through carefully designed endpoints that cover properties, listings, agents, and market metrics.
Optimized data pipelines deliver Realtor results in milliseconds. Low latency means a better experience for your end users.
Every Realtor endpoint returns clean, well-structured JSON that is ready to parse and use directly in your application logic.
From property valuation to market analysis, the Realtor powers a wide range of real estate applications.
Analyze Realtor property data to determine accurate market values, estimate appreciation, and identify undervalued investment opportunities.
Track Realtor listing trends, pricing shifts, and inventory changes to make informed, data-driven investment and development decisions.
Monitor your real estate portfolio with live Realtor data. Track current values, rental comps, and market conditions in one place.
Identify high-potential properties and neighborhoods using Realtor data to power targeted outreach and marketing campaigns.
Compare listings, pricing, and agent activity across Realtor to understand market positioning and stay ahead of competition.
Build real-time dashboards that aggregate Realtor data for internal teams, clients, or investors with always-current information.
Common questions about using the Realtor through RealtyAPI.
Get started with 250 free API calls. No credit card required.