Find property listings by MLS number (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Deprecated MLS-number search for maintaining and auditing older property lookup workflows. Supply the required mls_id string; optional limit and offset control the number of listings and the number skipped. The documented sort values are price_low, price_high, photos, newest, and open_house_date. An MLS number is not a guaranteed globally unique property identity, so retain MLS context when reconciling records. No live response was observed in the supplied evidence. An unverified documentation example contains a listings array, matching_rows and returned_rows counts, and a meta object. Example listing fields include property_id, listing_id, mls.id, mls.name, mls.abbreviation, address, address_new, beds, baths, prop_type, prop_sub_type, prop_status, price, price_raw, sqft, sqft_raw, photo_count, list_date, and last_update. The address_new object includes city, state_code, postal_code, lat, and lon. The example represents price and sqft as display strings, price_raw as a number, and sqft_raw as null; consumers should handle missing or null values rather than assuming uniform numeric fields. These example fields are not a verified current response contract. A current general property-search endpoint does not by itself establish an equivalent MLS-number filter; validate replacement behavior before migrating.

API Features

MLS-number lookup contract Preserves the required mls_id input for existing integrations without equating an MLS number with a globally unique property identifier.
Offset-based MLS result paging Documents optional limit and offset controls for traversing matching listings; no maximum page size is established by the supplied facts.
Five documented MLS sort choices Retains price_low, price_high, photos, newest, and open_house_date as the documented legacy sorting values.
Listing-to-MLS reconciliation fields Identifies property_id, listing_id, and nested mls fields in an unverified example so migration checks can preserve listing identity and MLS context separately.

Live API Demo

GET /api/project/realty-in-us/properties-list-by-mls-deprecated

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

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

Use Cases

Frequently asked questions

What does this deprecated MLS lookup require?

It requires mls_id as a string. limit, offset, and sort are optional. This endpoint documents an older MLS-number lookup contract rather than a recommended starting point for a new integration.

Is mls_id interchangeable with property_id or listing_id?

No. mls_id is the search input, while property_id and listing_id appear as separate fields in the documentation example. Retain the associated MLS context and do not assume an MLS number is globally unique.

How are MLS lookup results paged and sorted?

limit requests a number of items and offset skips that many items before the returned page. Documented sort values are price_low, price_high, photos, newest, and open_house_date. A maximum page size and a stable ordering guarantee were not supplied.

Were the MLS response fields confirmed by a live request?

No. Only an unverified documentation example was supplied. It shows listings, matching_rows, returned_rows, meta, and listing-level identity, address, price, room-count, area, and MLS fields. Their current presence and types are not confirmed.

Can a general property-list endpoint replace MLS-number lookup directly?

Not on the supplied evidence. Verify that the replacement explicitly supports the required MLS-number lookup and compare selected records with their original MLS context before migrating.

Related operations

Guides

View Subscription Plans →