Articles on: Property History

Accessing Historical Listings for an Address

When working with real estate listings, understanding the historical context of a property can be crucial. At Repliers, our API provides comprehensive access to both current and historical listing data. Here’s how you can access this information through our API.

History For Addresses With An Active Listing



For active listings (status: A), our API includes a "history" object within the listing data itself. This object contains an array of historical transactions for the address. Here's an example of what the history object might look like for an active listing:

{
    "history": [
        {
            "mlsNumber": "123455677XX",
            "type": "Sale",
            "listPrice": "499900.00",
            "listDate": "2024-05-11T00:00:00.000Z",
            "lastStatus": "Terminated",
            "office": {
                "brokerageName": "RE/MAX REALTY PEOPLE INC."
            },
            "timestamps": {
                "idxUpdated": "2024-06-09T16:57:49.000Z",
                "listingUpdated": "2024-06-09T16:57:49.000Z",
                "photosUpdated": "2024-05-11T18:02:32.000Z",
                "listingEntryDate": "2024-05-11T00:00:00.000Z",
                "expiryDate": "2024-12-31T00:00:00.000Z"
            }
        }
    ]
}


History For Addresses With No Active Listings



For unavailable listings (status: U), the history data is not automatically provided in a history object. To access the historical data for an address that isn't active you need to make a separate API request to the address history lookup endpoint.

Why A Separate Endpoint?

This approach is used because we do not retroactively update the history objects of unavailable listings to conserve resources. If we were to update the history object within each listing document every time a new transaction occurred, it would involve retroactively updating every historical record associated with that property. For properties with extensive transaction histories, this would mean updating numerous records, each time consuming considerable database resources and processing time.

Example Request

Here is an example of how you can make a request using the address history endpoint:

https://api.repliers.io/listings/history?streetNumber=101&streetName=Dalmations&streetSuffix=Cres&city=New York&zip=90000


For more information on the address history lookup endpoint please refer to our API documentation.

Updated on: 20/01/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!