Redfin API
Listings for sale, sold or for rent, the Redfin Estimate alongside the full MLS fact sheet, and region-level market statistics — median price, price per sqft and sale-to-list — as a single call rather than an aggregation job.
50 free credits on signup. No card, no MLS relationship.
{ "data": { "listing_status": "for_sale", "region": { "id": 30818, "type": 6, "url": "https://www.redfin.com/city/30818/TX/Austin", "service_area": "southwest-austin" }, "count": 100, "listings": [ { "position": 1, "property_id": 31521783, "listing_id": 222004156, "mls_id": "2165482223636189961" } ] }, "response_time": 2110, "credits_used": 1, "credits_remaining": 4710}Live call against the real endpoint — 3 free runs, then it's your own key.
What is the Scavio Redfin API?
The Scavio Redfin API is a REST API that returns public Redfin data as structured JSON. You send a region with a listing status, a property id or a region id to one of 3 POST endpoints with your API key, and get back listings with price per sqft, a property's Redfin Estimate and MLS fact sheet, or ready-made market statistics for the whole region.
- 3
- endpoints, all live in production
- 1
- credit per call, every endpoint
- 1
- call for a region's medians
Aggregates first, then the rows
Most housing questions are answered by the market endpoint alone.
Market statistics
POST /api/v1/redfin/marketMedian list and sale price, price per sqft and sale-to-list ratio for a whole region, in one call — the aggregate you would otherwise compute from thousands of listings.
Listing search
POST /api/v1/redfin/searchFor sale, sold or for rent with price per sqft already on the row, plus the MLS id — which is the key for reconciling against any other data source.
Property detail
POST /api/v1/redfin/propertyThe Redfin Estimate and a rental estimate alongside the complete MLS fact sheet — two independent valuations rather than one.
All 3 Redfin endpoints
Every route is a POST, returns JSON, and takes the same API key. 1 credit per successful call.
| Endpoint | Returns | Credits |
|---|---|---|
Listing search/api/v1/redfin/search | For sale, sold or for rent — price, price per sqft, beds, baths, area | 1 |
Property detail/api/v1/redfin/property | Redfin Estimate, rental estimate and the complete MLS fact sheet | 1 |
Market statistics/api/v1/redfin/market | Median list and sale price, price per sqft, sale-to-list, by region | 1 |
50 free credits on signup covers 50 calls of any kind. See plans
A region's medians without aggregating anything
One call returns median sale price and sale-to-list. The response on the right is a real capture, field names and all.
from scavio import ScavioClient
client = ScavioClient(api_key="sk_live_your_key")
# Region-level stats in ONE call, no aggregation required
stats = client.redfin.market(region_id=30818)
print(stats["data"]["median_sale_price"], stats["data"]["sale_to_list"])
# Or walk the listings behind them - 1 credit
res = client.redfin.search(location="78701", listing_status="for_sale"){
"data": {
"listing_status": "for_sale",
"region": {
"id": 30818,
"type": 6,
"url": "https://www.redfin.com/city/30818/TX/Austin",
"service_area": "southwest-austin"
},
"count": 100,
"listings": [
{
"position": 1,
"property_id": 31521783,
"listing_id": 222004156,
"mls_id": "2165482223636189961"
}
]
},
"response_time": 2110,
"credits_used": 1,
"credits_remaining": 4710
}Why not go direct?
Redfin publishes no developer API, so the alternative is building and maintaining it.
Building it yourself
- Redfin has no public developer API; data partnerships are commercial arrangements
- Region statistics would have to be aggregated from full listing pulls
- Listing, property and MLS ids all differ, so reconciliation is its own project
- Search responses are behind an internal endpoint whose shape changes without notice
Scavio Redfin API
- One API key, issued at signup — no partnership, no MLS agreement
- Region medians and sale-to-list as a single documented call
- Redfin Estimate and rental estimate together on property detail
- Same key and JSON envelope as 30 other Scavio platforms
Scavio returns publicly available listing and market data only, and never authenticates as a Redfin user.
What developers build with it
Market reporting without the aggregation
Median sale price, price per sqft and sale-to-list ratio for a region come back in a single call. Building the same numbers from listings means pulling thousands of rows and hoping your methodology matches everyone else's.
marketBuy-side and investment screening
Compare sale-to-list across regions to find where sellers are conceding, then walk the listings behind the statistic to find specific candidates.
market + searchDual-valuation checks
Property detail returns the Redfin Estimate and a rental estimate together, so a purchase price can be sanity-checked against both resale value and yield in one call.
propertyCross-source reconciliation
Search rows carry the MLS id alongside Redfin's own property and listing ids, which is what lets you join Redfin against Zillow or an MLS feed without fuzzy address matching.
searchPropTech dashboards
Feed market statistics and live inventory into a dashboard with one key, using Zillow through the same envelope as a second opinion on valuation.
market + search + ZillowHow to get Redfin data as JSON
- 1
Get an API key
Sign up for a Scavio account and copy your key from the dashboard. You get 50 credits free on signup, with no card required and no MLS or brokerage relationship.
- 2
POST a region and a listing status
Send {"location": "78701", "listing_status": "for_sale"} to https://api.scavio.dev/api/v1/redfin/search. Redfin will not accept a city string — location must be a 5-digit ZIP or a Redfin region URL. The response echoes the resolved region and its id.
- 3
Use market for aggregates, search for rows
If you want the median, call /market — it is 1 credit and returns the statistic directly. Only page listings when you need the individual properties behind the number.
Redfin API FAQ
What is the Scavio Redfin API?
+
It is a REST API that returns public Redfin data as structured JSON. Three POST endpoints cover listing search across for-sale, sold and for-rent inventory, full property detail with the Redfin Estimate and MLS fact sheet, and region-level market statistics. You authenticate with a Scavio API key.
Who are these endpoints for?
+
Real estate investors and analysts tracking markets; developers building PropTech dashboards; AI agent builders wiring Redfin in as an MCP or SDK tool; automation engineers running alerts inside n8n, Zapier or Make; brokerages benchmarking regions; and journalists reporting housing trends. Same API for all of them.
What makes the market endpoint useful?
+
It returns median list price, median sale price, price per sqft and sale-to-list ratio for a region as a single 1-credit call. The alternative is pulling every listing and aggregating yourself, which costs far more and produces a number nobody else can reproduce.
How is this different from Zillow?
+
Zillow gives you complete price history per property and the Zestimate; Redfin gives you the Redfin Estimate, a rental estimate, the MLS fact sheet and — uniquely — ready-made region statistics. Running both through the same JSON envelope gives you two independent valuations to compare.
Does Redfin have a public API?
+
No. Redfin has no public developer API. Its data partnerships are commercial arrangements, so for reading public listings and market statistics there is no first-party self-serve option.
How much does a Redfin request cost?
+
Every Redfin endpoint costs 1 credit, market statistics included. New accounts get 50 free credits on signup, one time, with no card required. Paid plans start at $30 per month for 7,000 credits.
What does the response look like?
+
The API wraps the payload under a data key and adds credits_used and credits_remaining. A search echoes listing_status and a resolved region object with id, type, url and service_area, and each listing carries position, property_id, listing_id and mls_id.
Why are there three different ids on a listing?
+
property_id and listing_id are Redfin's own — a property persists across multiple listings over time, while a listing is one attempt to sell it. mls_id is the external key, which is what you join on when reconciling against another source.
Which languages and tools are supported?
+
Official Python (pip install scavio) and JavaScript/TypeScript (npm i scavio) SDKs, a remote MCP server at mcp.scavio.dev for AI agents, and an n8n community node. Any language can call the REST endpoints directly with an HTTP client.
Is scraping Redfin data legal?
+
Scavio returns publicly available listing and market data and does not authenticate as a user. Listing data may also be subject to MLS rules depending on how you redistribute it. Talk to your own counsel for your specific use case.
Explore more of Scavio
Zillow API
Listings, price history and Zestimates.
Airbnb API
Stays, the price ledger and review bodies.
Google Maps API
Local search, places and reviews.
SEC EDGAR API
Filings, XBRL facts and full-text search.
MCP server
Every platform as a callable tool for agents.
Pricing
Credit packs and plans, no per-platform surcharge.
Start pulling Redfin data today
50 free credits on signup, no card. Your first request is a POST with a city in it.