Listing search monitoring
Use Redfin endpoints to turn listing search monitoring into repeatable API requests with documented inputs and JSON responses.
Use a Redfin API to turn public Redfin listing search, property detail, Redfin Estimate, comparables, and regional market-trend pages into structured JSON for real estate research, valuation, and market-monitoring workflows.
Use a Redfin API to collect listing search, property detail, Redfin Estimate, and regional market-trend data as structured JSON for real estate intelligence.
Endpoint families
5
Documented params
21
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
8
Schema refs
5
{
"platform": "Redfin",
"endpoint": "redfin-search",
"method": "GET",
"path": "/redfin/search",
"auth": "apiKey"
}Free tools
Use cases
Use a Redfin API to collect listing search, property detail, Redfin Estimate, and regional market-trend data as structured JSON for real estate intelligence.
Use Redfin endpoints to turn listing search monitoring into repeatable API requests with documented inputs and JSON responses.
Use Redfin endpoints to turn property valuation with redfin estimate into repeatable API requests with documented inputs and JSON responses.
Use Redfin endpoints to turn regional market trend analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Redfin endpoint catalog — 5 endpoints, 21 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Redfin endpoints, grouped into 5 request families — Estimate, Property and Region Trends, plus 2 more.
21 request parameters are documented across those Redfin endpoints, 8 of them required — the full input contract is public before you write any integration code.
5 of the 5 Redfin endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Redfin endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the Redfin endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/redfin/estimate
/redfin/property
/redfin/region-trends
/redfin/search
/redfin/similar
Endpoint catalog
/redfin/estimateReturns the Redfin Estimate for a property, including the current estimate, property facts, and the monthly estimate history with city/county/postal comparatives. Faithful pass-through of Redfin's public avm + avmHistoricalData resources.
MCP tool redfin_estimate
/redfin/propertyReturns normalized Redfin public property details. Provide a listing url, or a property_id (optionally with listing_id) to use Redfin's public stingray detail API.
MCP tool redfin_property
/redfin/region-trendsReturns Redfin's aggregate market trends for a region (median list/sale price, sale-to-list, offers, days on market, inventory, year-over-year). Faithful pass-through of Redfin's public aggregate-trends resource.
MCP tool redfin_region_trends
/redfin/searchReturns normalized Redfin public listing search results from Redfin's credential-free region CSV endpoint. Pass region_id/region_type from autocomplete to skip location resolution.
MCP tool redfin_search
/redfin/similarReturns Redfin's comparable ("similar") listings for a property as normalized listing rows. Faithful pass-through of Redfin's public similars resource.
MCP tool redfin_similar
Related APIs
Real Estate & Property
Use a Zillow API to turn public property search, home detail, and location autocomplete pages into structured JSON for real estate research, market monitoring, and property intelligence workflows.
Real Estate & Property
Turn Rightmove — the UK's largest property portal — into structured JSON: location autocomplete, for-sale/to-let/sold property search with price and bedroom filters, dedicated commercial, new-homes and student-accommodation searches, estate-agent branch listings, and full property detail including floor plans, EPC rating, and nearby schools, all with one API key.
How to scrape Redfin
Redfin property data complements Zillow for real-estate intelligence. Crawlora's Redfin endpoints return search, property, and estimate data as structured JSON.
Search a region with filters, look up a single property, or pull the Redfin Estimate.
Pass the region/filters or a property reference to Crawlora's Redfin endpoint.
Receive price, beds, baths, square footage, status, Redfin Estimate, and price history as clean JSON.
Re-run on a schedule to track price cuts, new listings, and sold prices across a region.
FAQ
Send a Redfin region search or property URL to Crawlora's Redfin endpoint and get structured JSON — price, beds/baths, sqft, status, Redfin Estimate, history — without rotating proxies. Collect public data and respect Redfin's terms.
Yes — Crawlora returns both Redfin and Zillow in a normalized shape, so you can cross-reference listings, estimates, and history for the same property across sources.
Collecting publicly visible listing data is generally permissible if you respect Redfin's terms of use, robots directives, rate limits, and applicable law. This is for public data you're authorized to collect.
No. Redfin does not offer a public API, self-serve API keys, or per-property REST endpoints for developers — its official Data Center provides only aggregate regional market-trend CSV downloads, not individual listing or property records. Crawlora's Redfin endpoints return per-property listing search, detail, Redfin Estimate, and market-trend data as structured JSON with a single API key.