/redfin/properties

POST /api/redfin/properties

Price: 5 credits

Get full Redfin property details by property URL: address, price, predicted value, last sold price/date, beds, baths, sqft, lot size, year built, stories, property type, HOA, MLS id and status, days on market, latitude/longitude, photos, listing description, listing agents/brokers and the full amenity breakdown (parking, interior, exterior, utilities, etc.).

How to use it

Fetch a single Redfin property by its URL or path (must contain /home/{id}, e.g. from the property search endpoint). Returns one item with id, listing_id, url, mls_id, status, price, price_per_sqft, predicted_value, last_sold_price/date, beds, baths, full/partial baths, sqft, lot_size, year_built, stories, property_type, days_on_market, hoa_fee, full address fields, county, apn, latitude/longitude, description, image+images, listing_agents (name/broker) and amenity_groups (title + name/values).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Redfin property URL or path (containing /home/{id}) (examples: "https://www.redfin.com/NY/Brooklyn/7017-20th-Ave-11204/home/171337321", "/NY/Brooklyn/7017-20th-Ave-11204/home/171337321"; minLength: 1)

Response

• @type string (default: "RedfinProperty")
• id string required
• listing_id string nullable
• url string nullable
• mls_id string nullable
• status string nullable
• status_description string nullable
• price number nullable
• price_per_sqft number nullable
• predicted_value number nullable
• last_sold_price number nullable
• last_sold_date integer nullable
• beds number nullable
• baths number nullable
• full_baths integer nullable
• partial_baths integer nullable
• sqft integer nullable
• lot_size integer nullable
• year_built integer nullable
• stories number nullable
• property_type string nullable
• days_on_market integer nullable
• days_on_market_label string nullable
• hoa_fee number nullable
• street_address string nullable
• unit_number string nullable
• city string nullable
• state string nullable
• zip string nullable
• country_code string nullable
• full_address string nullable
• county string nullable
• apn string nullable
• latitude number nullable
• longitude number nullable
• description string nullable
• image string nullable
• images array (default: [])
• listing_agents array (default: [])
  • @type string (default: "RedfinAgent")
  • name string nullable
  • broker_name string nullable
  • is_redfin_agent boolean nullable
• data_source string nullable
• amenity_groups array (default: [])
  • @type string (default: "RedfinAmenityGroup")
  • amenities array (default: [])
    • @type string (default: "RedfinAmenity")
    • name string required
    • values 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 — Property not found (well-formed URL but no property data for it) 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.