Skip to content
RealtyDataAPI
Parcel & Building Intelligence · Payload Slimming8 min read·Updated 2026-11-15

Redfin API & Parcel Data Guide (2026): Streamlined MLS, APN, HOA & Multi-Unit Building JSON

Quick Answer (BLUF)

Redfin does not offer a public developer API, and scraping internal Redfin Stingray/GIS endpoints triggers immediate HTTP 403 blocks while returning massive 228-row, 1.2MB+ nested JSON blobs that overflow LLM context windows. RealtyData API's GET /v1/redfin/search slices results cleanly to your requested limit (1–50), strips 92% of UI bloat, and returns normalized parcel specs (MLS ID, HOA dues, price/sqft, DOM, lat/lng) plus multi-unit condo/apartment building summaries at 2 Credits ($0.08–$0.20/1K) per parcel.

Gateway p50 Latency22ms cached (<280ms warm · 1.8s live)
Concurrency & Rate Limit60 – 600 RPM (Dual-Rail Failover)Need 1,000+ RPM? Dedicated Enterprise Key Pool available
Deterministic Unit Price$0.08–$0.15 / 1,000 listings

Instant rl_live_... key in 3s (12,000 Free Credits + 20,000 Sandbox Streak Credits) · $1 = 10,000 Credits · 0 Credits on empty queries · Top up anytime via 0%-fee Multi-Chain Crypto (+5% bonus credits, never-expiring PAYG)

Instant Quickstart · Copy & Run in 30 Seconds

Fetch Streamlined Redfin Parcels + Building Rollups (Downtown Austin 78701)

import requests

res = requests.get(
    "https://api.realtydataapi.com/v1/redfin/search",
    params={"location": "78701", "limit": 5},
    headers={"x-api-key": "rl_live_your_api_key"},
    timeout=30,
).json()["data"]

print(f"Showing {res['count']} of {res['total_parcels_matched']} Redfin parcels")
for p in res["properties"]:
    print(p["formatted_address"], f"${p['list_price']:,}", f"HOA: ${p.get('hoa_fee_monthly')}/mo")
Want to inspect real live MLS & valuation JSON before creating an account?Try 3 Free Live Runs in Browser Playground (No Login) →

Key Engineering Takeaways (TL;DR)

  • ✓92% smaller JSON payload: slices raw 228-parcel blobs to your exact ?limit=20 parameter while keeping total_parcels_matched.
  • ✓Unique multi-unit building intelligence: returns buildings_summary alongside individual condo/apartment units for high-rise & multifamily analysis.
  • ✓Preserves hard-to-get parcel fields: monthly HOA fees, MLS numbers, price per sq.ft, days on market, and exact parcel lat/lng coordinates.
  • ✓Ideal for Claude, ChatGPT, and Cursor MCP agents where compact, high-signal JSON prevents token window exhaustion.

1. Why Direct Redfin GIS-CSV & Stingray Scraping Breaks in Production

Data scientists have historically relied on unofficial Redfin CSV downloads or internal Stingray JSON endpoints, but 2026 anti-bot defenses make DIY scraping unsustainable.

  • WAF & TLS Fingerprinting: Datacenter IPs from AWS, GCP, Hetzner, and Vercel receive instant 403 challenge pages unless routed through costly residential proxy rotations.
  • 1.2MB Payload Bloat: A single ZIP code response contains 200+ homes with dozens of internal UI flags, obfuscated key arrays, and polygon strings that waste bandwidth and LLM input tokens.
  • Region ID Indirection: Internal Redfin routes require resolving proprietary region_id and region_type integers before you can even query a 5-digit ZIP code.
GET /v1/redfin/search vs Direct Redfin Stingray / CSV Scraping
Technical MetricRealtyData API (/v1/redfin/search)Direct Stingray ScrapingAsync Browser Actor
Input ParameterDirect ?location=78701 or Austin, TXRequires region_id + region_type lookupFull Redfin search URL
Payload Size (20 Parcels)~6.8 KB clean JSON1,150+ KB raw nested blob450+ KB raw dataset dump
Multi-Unit Building RollupIncluded (buildings_summary[])Buried in undocumented sub-keysOften dropped by HTML parsers
Latency25–40 ms cached · 1.8–3.4 s liveBlocked / 403 without proxies25–60 s container cold start

2. Querying Redfin Parcels & Condo Building Summaries in Python & Node.js

Pass any ZIP code or city to GET /v1/redfin/search to inspect active parcel inventory and high-rise building unit counts simultaneously.

Fetch Streamlined Redfin Parcels + Building Rollups (Downtown Austin 78701)

Cost: 2 Credits per parcel returned (e.g., limit=5 -> 10 Credits = $0.001 PAYG / $0.0004 Business).

curl -sS "https://api.realtydataapi.com/v1/redfin/search?location=78701&limit=5" \
  -H "x-api-key: rl_live_your_api_key"
Test this exact endpoint right now in your browser (3 free anonymous runs):Run 3 Free Live Queries in Playground →

Interactive PropTech Underwriting Terminal · GET /v1/redfin/search

Verify real-time latency, parcel credit math & JSON schema

10,000 listings/day
2,000 dossiers/day
5,000 records/day
HTTP Calls / Day
2,750
5 Unified Routes
Credit Unit
$1 = 10,000
$9 Indie Pack Ready
Empty / 404 Fee
0 Credits
$0.00 on 0 matches
Estimated Monthly Pipeline Cost (30 Days)
$60.00/ mo on Business ($86.25 on Pro)
Monthly consumption: 1,500,000 Credits (50,000 Credits/day)
RealtyData API (Business $0.08/1K records):$60.00 / mo
RealEstateAPI / RentCast ($20/1K records):$10200.00 / mo
Empty ZIP search / unfound property fee:$0.00 (0 Credits)

Frequently Asked Questions

When should I use /v1/redfin/search vs /v1/properties/search?
Use /v1/properties/search as your primary MLS + AVM + Rent Estimate engine, and pair it with /v1/redfin/search when you want Redfin-specific MLS coverage, HOA-heavy urban condo buildings (buildings_summary), or cross-portal parcel verification.
Does /v1/redfin/search charge for all 228 matched homes or only the sliced limit?
You only pay 2 Credits per parcel actually returned in properties[] (up to your limit parameter), never for the unreturned remainder!
Are upstream aggregator headers or third-party proxy fingerprints ever exposed?
Never. Every response is sanitized, normalized, and served directly from api.realtydataapi.com.