Changelog

Added comprehensive documentation for sale-related filter parameters in Property Search API, including examples and use cases for filtering by sale dates, sale prices, arms-length transactions, and other sale-related criteria.

Response schema fields and their types are now documented under the "Responses" section with 200 status code for all main API reference pages. This includes field names, data types, and string enumerations. Swagger docs remain available and will stay most up-to-date until documentation automation is complete.

MLS Search API documentation has a new look and feel with improved navigation and readability. The updated design makes it easier to find endpoint information, parameters, and response examples.

Property Search API documentation has a new look and feel with improved navigation and readability. The updated design makes it easier to find endpoint information, parameters, and response examples.

Resolved data inconsistencies between MLS Search and MLS Detail APIs. Listings should now return consistent information whether accessed through search results or detail endpoints.

Resolved issue where photos, open houses, and other listing details were randomly missing on some listings in MLS Detail API responses. All available listing data should now populate consistently.

Resolved pipeline bugs that caused random listings to go missing during previous data loads. This fix ensures more consistent and complete listing availability across all MLS boards.

Resolved issue where legacy listing IDs returned 404 errors or null data responses on MLS Detail API. Listings can now be accessed using previously cached IDs via the priorId field, preventing workflow disruptions from ID changes.