Search US properties for sale, rent or sold listings

View all Realty in US Property & Mortgage Data endpoints →

Search residential listings with POST /properties/v3/list and an optional JSON request body. The documented body fields are state_code (string), status and type (arrays), list_price, beds, baths and sort (objects), cats and dogs (booleans), and limit and offset (integers). No body parameter is marked required. A successful HTTP 200 probe used state_code="CA", status=["for_sale"], limit=3, offset=0 and sort={"direction":"desc","field":"list_date"}. That probe verifies this California for-sale request, not every state, status, property type or filter combination. Nested schemas for list_price, beds and baths, additional sort values, array enums and pet-filter behavior were not established by the supplied evidence; do not import a ZIP-code body or filter syntax from another route. The observed response contains data.home_search.count, total and results. The sample returned count=3 and three results while total=161224 described the broader matching set, not the number of rows on the page. Observed result fields include property_id, listing_id, status, list_price, list_date, last_sold_date and last_sold_price; location.address contains line, city, postal_code, state_code, state, country and coordinate. The description object includes type, sub_type, beds, baths, baths_full and sqft. Additional observed fields such as primary_photo, photo_count and some size and flag values can be null. Keep property_id and listing_id distinct for subsequent lookups. The sample had California addresses and 2026-10-22 listing dates; those observations do not establish complete inventory, a real-time update guarantee or non-null data for every listing. No separate source response example is supplied for this operation; the listed response fields come from the successful probe.

API Features

State-and-status listing discovery A successful request combined state_code CA with status ["for_sale"]. Sale, rent and sold search are documented purposes, but additional status literals were not verified.
Search-page counts versus total matches The observed data.home_search envelope separates count and results for the returned page from total across the matching set: three rows were returned from 161224 matches.
Listing-date sort with offset pagination The verified request used limit 3, offset 0 and sort direction desc on field list_date, supporting a small first page without asserting a stable snapshot or unlimited page sizes.
Search rows with both home and listing IDs Observed results retain property_id and listing_id alongside asking price, listing date, address and home attributes for selecting records before more detailed lookups.
Typed optional search-filter surface The body exposes object-valued price, bedroom and bathroom filters, array-valued property types, and boolean cat and dog filters; their detailed schemas and untested behavior need validation.

Live API Demo

POST /api/project/realty-in-us/properties-v3-list

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X POST 'https://api.opendata-api.com/api/project/realty-in-us/properties-v3-list?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What request was successfully tested for property search?

An HTTP 200 response was observed for a JSON body with state_code "CA", status ["for_sale"], limit 3, offset 0 and sort {"direction":"desc","field":"list_date"}. This verifies that combination, not every possible filter.

Does count represent every matching property?

No. In the observed data.home_search response, count was 3 and results contained three listings, while total was 161224. Treat count as the returned-page count and total as the matching-set total in that response.

Which fields can I use to identify and display search results?

The observed results include property_id, listing_id, list_price, list_date, status, location.address and a description object with fields such as beds, baths and sqft. Preserve both identifiers; a property ID and a listing ID are not interchangeable. Some values, including primary_photo in the inspected row, are null.

Are the exact price, bedroom and bathroom range schemas documented here?

No. list_price, beds and baths are optional objects, but their nested keys and range semantics are not defined by the supplied facts or exercised in the verified request. Do not assume min/max keys or copy a body from another endpoint.

Can I use this operation for rental and sold-property searches?

Sale, rent and sold listing search are documented purposes. Only the status array ["for_sale"] was observed in a successful probe; rental and sold status literals, pet filters and property-type values still require validation.

Do recent listing dates prove that this is a complete real-time inventory feed?

No. The sample included California addresses and 2026-10-22 list_date values. A single successful page does not establish complete market coverage, a freshness service level or stable results while paging.

Related operations

Guides

View Subscription Plans →