/redfin/properties/search

POST /api/redfin/properties/search

Price: 20 credits

Search Redfin homes for sale in a region (city/neighborhood/ZIP region id). Returns property cards with price, beds, baths, sqft, price_per_sqft, lot_size, year_built, property_type, full address (street_line, city, state, zip), latitude/longitude, days_on_market, MLS id and status, listing agent/broker, description and key facts.

How to use it

Search homes for sale within a Redfin region. region_id is the numeric id from the region's Redfin URL (/city/{id}/... -> region_type 6, /neighborhood/{id}/... -> region_type 1, /zipcode/{id}/... -> region_type 2). Each item has id (property id), listing_id, url, mls_id, mls_status, price, hoa, beds, baths, sqft, price_per_sqft, lot_size, year_built, property_type, street_line/unit_number/location/city/state/zip, latitude/longitude, days_on_market, photo_count, listing_agent, listing_broker, description, key_facts and listing_tags. Use the returned id with the Redfin property endpoint for full details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region_id string required — Numeric Redfin region id, taken from the region page URL (e.g. /city/30749/NY/New-York -> 30749, /neighborhood/3040/... -> 3040) (examples: "30749", "16163"; minLength: 1)
• region_type integer required — Region type: city, neighborhood, zip, county, or school district (one of: 1, 2, 4, 6, 7)
• count integer required — Max number of homes to return (min: 1)

Response

• @type string (default: "RedfinHomeCard")
• id string required
• listing_id string nullable
• url string nullable
• mls_id string nullable
• mls_status string nullable
• price number nullable
• hoa number nullable
• beds number nullable
• baths number nullable
• sqft integer nullable
• price_per_sqft number nullable
• lot_size integer nullable
• year_built integer nullable
• property_type string nullable
• stories number nullable
• street_line string nullable
• unit_number string nullable
• location string nullable
• city string nullable
• state string nullable
• zip string nullable
• country_code string nullable
• latitude number nullable
• longitude number nullable
• days_on_market integer nullable
• photo_count integer nullable
• listing_agent string nullable
• listing_broker string nullable
• is_redfin boolean nullable
• is_new_construction boolean nullable
• has_3d_tour boolean nullable
• description string nullable
• key_facts array (default: [])
• listing_tags array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.