Legacy v2 MLS property lookup (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Look up legacy property listings by the required mls_id. The optional prop_status filter accepts for_sale, for_rent, or recently_sold; limit controls the number of items requested and offset skips items for pagination. Retain MLS source and listing-status context when comparing records: the documentation does not establish global uniqueness of an MLS number. Response documentation, not observed output: the supplied source example contains meta.matching_rows and meta.returned_rows plus a properties array. Illustrated property fields include property_id, listing_id, price, beds, baths, baths_full, prop_status, prop_type, prop_sub_type, photo_count, and last_update. The address object includes line, city, state, state_code, postal_code, lat, and lon; the mls object includes id, abbreviation, name, and type. These fields come from an unverified source example, and no probe response is available for this operation. Their current presence, completeness, and availability are not confirmed. This deprecated route is retained to document legacy MLS-number workflows and migration requirements, not as a recommended entry point for new integrations or a complete MLS feed. Do not assume that a current general property search accepts the same MLS-number query.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/realty-in-us/properties-v2-list-by-mls-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v2-list-by-mls-deprecated?key=<API_KEY>&mls_id=<mls_id>'
Query Result
Use Cases
- Inventory an older MLS-number lookup and record its required mls_id before replacing the route.
- Preserve for_sale, for_rent, or recently_sold context when comparing legacy MLS lookup results with migrated records.
- Document how a previously paged MLS lookup used limit and offset so a replacement does not silently inspect only its first page.
- Compare historical MLS source, property identifiers, and addresses against a separately verified replacement contract without assuming identical MLS-number support.
Frequently asked questions
Which input is required for the legacy MLS lookup?
mls_id is the only required query parameter in this contract. The documented example is OLRS-1293107. limit, offset, and prop_status are optional; an MLS number should retain its source context rather than be treated as a proven globally unique property identifier.
Which listing statuses can prop_status select?
The documented values are for_sale, for_rent, and recently_sold. Preserve the exact token, including underscores, when documenting an existing lookup. The available evidence does not verify present-day matches for any status.
How does pagination work for an MLS-number request?
limit requests a number of items and offset identifies how many items to skip. The documented examples are 10 and 0 respectively. They are examples, not confirmed server defaults or maximum limits.
Are the MLS lookup response fields verified by a probe?
No. An unverified source example shows meta.matching_rows, meta.returned_rows, and properties entries with property_id, listing_id, mls, address, price, and listing-status fields. No probe response confirms their current availability or completeness.
Can a new property search be substituted for this MLS route without changes?
No equivalence is established. This route is deprecated and retained for migration reference. Verify whether a replacement accepts MLS numbers and preserves source, status, and paging intent instead of copying this query into a different operation.