> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.repliers.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# API Server Changelog

Sep 17, 2026
* `POST /nlp` - now supports open house searches (e.g. "open houses this weekend");
* `POST /nlp` - Canadian forward sortation areas in prompts (e.g. `M2J`)
* `POST /nlp` - improved handling of zip and postal codes in prompts
* `GET /locations/autocomplete` - new `locationId` parameter; fixed some `LiveBy` locations not being found
* `GET /locations` - `locationId` accepts up to 50 values; stability fixes
* `GET /members` - `boardId` fixes
* `GET /partners/har/listings/views`, `GET /partners/har/listings/reviews` - responses now include `officeMlsId`

Sep 11, 2026
* `GET /listings` - fixed missing `grp-yr`/`grp-mth`/`grp-day` statistics buckets when `standardStatus` is used; date buckets with no data are now returned with zero counts across the requested date range
* `GET /listings` - stability fix when `aggregates` is passed as an array

Sep 8, 2026
* `GET /listings`, `GET /listings/:listingId`, `GET /favorites` - `duplicates` and `duplicatesDetails` fixes for multi-board API keys
* `GET /favorites` - fixed favorites not being returned for some boards

Sep 4, 2026
* `GET /locations` - `resultsPerPage` is no longer hard-capped at 300 (limit is now account-configurable)
* `GET /members`, `GET /offices` - responses now include `mlsName`

Sep 2, 2026
* `GET /listings` - `map` parameter can now be treated as standard GeoJSON (first ring is the outer boundary, subsequent rings are holes) - available on request
* `GET /listings/history` - blank query parameters (e.g. `zip=`) are now treated as absent instead of failing validation
* `GET /locations` - `PublicRecord` locations fixes
* `POST /nlp` - relative date phrases ("today", "last 7 days") are resolved against the current date; response includes `imagesHost` when `listings=true`; stability fixes
* `POST /estimates` - stability improvements for off-market price adjustment

Aug 28, 2026
* `GET /listings` - sold statistics (`cnt-closed`, `avg-soldPrice`, `med-soldPrice`, `pct-aboveBelowList`, etc.) now work with `standardStatus` (`Closed`, `Expired`, `Pending`, `Canceled`, `Incomplete`) instead of requiring `status=U`
* `GET /listings` - `brokerage` parameter now accepts multiple values and the `not:` prefix operator

Aug 26, 2026
* `GET /listings/history` - fixed missing listings when street suffix / direction abbreviations differ between boards (e.g. `Ave` vs `Avenue`)
* `GET /partners/har/showingsmart/logs` - new `brokerType` parameter (`Listing | Showing`)
* `GET /listings`, `POST /searches` - stability fixes

Aug 25, 2026
* `GET /favorites` - now supports `standardStatus` filter
* `GET /listings/history`, `GET /listings/:listingId` - fixed ordering of history entries
* `POST /estimates` - model validation errors now return `422` instead of `500`

Aug 24, 2026
* `POST /estimates` - lookback estimates improvements

Aug 12, 2026
* `GET /listings` - `contains:` operator on `details.description` and address fields is now significantly faster
* `GET /listings/:listingId` - fixed `history` discrepancy with `GET /listings/history` (both now use the same address matching and `addressKey`)
* `GET /locations` - fixed some MLS locations not being returned

Aug 7, 2026
* `GET /listings` - response now includes `unrecognizedParams` array listing query / body parameters that were not recognized
* `GET /listings` - new statistics `min-priceSqft`, `max-priceSqft`
* `GET /listings` - `daysOnMarket` and `priceSqft` statistics no longer require `status=U` and are now computed for active listings too
* `GET /listings` - fixed swapped `avgPriceLow/avgPriceHigh` and `medPriceLow/medPriceHigh` in `sqft` statistics
* `GET /listings` - stability fixes for `raw.*` field filters

Aug 6, 2026
* `GET /listings` - fixed `aggregatesUnique` for `raw.*` and `reso.*` fields
* `GET /listings` - performance improvements

Aug 3, 2026
* `GET /partners/har/*` - responses enriched with listing data and agent names; `listingKey` is returned as `mlsNumber`; default sort on showingsmart logs

Jul 31, 2026
* API server performance improvements

Jul 29, 2026
* `POST /estimates` - on-market model is now used for properties with MLS history; comparables are returned from the model and enriched with listing info; `listPrice` accepted for on-demand estimates

Jul 25, 2026
* `POST /estimates` - new on-market estimates model

Jul 24, 2026
* `GET /listings` - new `sortBy` values: `closedDateAsc`, `closedDateDesc`
* `GET /listings` - `aggregates` now supports `commercial.*`, `lot.*`, `details.waterfront`, `details.HOAFee2`, `details.HOAFee3`, `lastPriceChangeType`, `assignment`, `size`
* `GET /listings` - search performance improvements
* `GET /partners/har/*` - new params `boardAgentId` (views, reviews), `listingBoardAgentId`, `showingBoardAgentId` (showingsmart); updated `sortBy` columns

Jul 22, 2026
* `GET /listings` - fixed `standardStatus=Coming Soon` filtering for some boards
* `GET /listings` - Smart Rules improvements for TRREB

Jul 21, 2026
* `GET /listings` - new statistic `med-priceSqft`
* `GET /listings` - low-confidence image classifications are no longer returned in `imageInsights`
* `GET /listings`, `POST /searches` - improved validation of numeric params (`minBeds`, `maxYearBuilt`, `minParkingSpaces`, ...); out-of-range values now return `400` instead of `500`
* `POST /searches` - stability fixes

Jul 17, 2026
* `GET /members` - fixed `officeId` filtering
* `GET /listings` - `clusterFields` now respects `boardId`
* API server performance improvements

Jul 15, 2026
* API server performance improvements

Jul 1, 2026
* API server stability improvements

Jun 30, 2026
* `GET /listings` - `grp-yr`/`grp-mth`/`grp-day` statistics now bucket by `closedDate` when `minClosedDate`/`maxClosedDate` are used (`soldDate` otherwise); combining `minSoldDate/maxSoldDate` with `minClosedDate/maxClosedDate` now returns a validation error
* `GET /locations` - fixed `500` when aggregating on `address.area`

Jun 29, 2026
* `GET /listings` - `raw.*` fields now work inside body `queries`
* `GET /listings` - stability improvements

Jun 27, 2026
* `GET /listings` - fixed `lot.squareFeet` holding an acres value for select boards

Jun 23, 2026
* `GET /favorites` - new `sortBy` parameter (same values as `GET /listings`) plus `lat`/`long` for distance sorting
* `GET /locations`, `GET /locations/autocomplete` - `radius` search now also returns locations whose boundary intersects the radius (previously matched by center point only)

Jun 19, 2026
* `GET /listings` - address search improvements
* `POST /estimates` - stability fixes

Jun 18, 2026
* `GET /locations` - new `source=PublicRecord` and `type=property` for public-record property locations (available on request)
* `POST /nlp` - stability fixes

Jun 12, 2026
* `GET /listings` - stability fixes (invalid `map` input no longer returns `500`)
* `GET /listings/:listingId/similar` - stability fixes
* `GET /locations` - fixed some `LiveBy` locations not being returned

Jun 9, 2026
* `GET /clients` - stability improvements
* `GET /listings/history` - improved fetching of archived listings history

Jun 8, 2026
* `GET /listings` - fixes for `standardStatus` filtering and aggregations
* `GET /brokerages` - fixed `boardId` filtering for API keys with access to multiple boards
* `GET /offices` - fixes
* `GET /locations` - `LiveBy` locations are now correctly scoped to the boards the API key can access

Jun 5, 2026
* `GET /listings` - now properly supports `standardStatus` as both a filter and an aggregate field

Jun 3, 2026
* `GET /partners/har/listings/views`, `GET /partners/har/showingsmart/logs`, `GET /partners/har/listings/reviews` - new HAR partner integration endpoints

May 28, 2026
* `GET /listings` - new `pretty` parameter; when set to `true`, response fields are returned in a consistent canonical order (also on `POST /listings`, `GET /listings/:listingId`, `GET /listings/:listingId/similar`, `GET /listings/history`)
* `POST /nlp` - stability fixes

May 26, 2026
* `GET /listings` - new `sortBy` values: `listPricePerSqFtAsc`, `listPricePerSqFtDesc`, `soldPricePerSqFtAsc`, `soldPricePerSqFtDesc`
* `GET /listings` - requesting `fields=*` now also returns computed fields (`boardId`, `simpleDaysOnMarket`, `standardStatus`)

May 25, 2026
* `GET /listings` - fixed `standardStatus` returning `Active` instead of `Coming Soon` for coming-soon listings

May 22, 2026
* `POST /messages` - stability fixes

May 20, 2026
* `GET /places` - new `inputInsidePolygon` parameter. When set to `true`, returns only entries whose polygon contains the queried point; each entry now also includes an `inputInsidePolygon` flag
* `POST /accounts` - now enforces a per-email API-key limit (returns `403` once the maximum is reached)

May 19, 2026
* `POST /estimates` - improved field-value handling using unique aggregates (fixes missing values for some boards)

May 12, 2026
* `POST /estimates` - improved city selection (now uses the most frequent city among matching listings)

May 11, 2026
* `GET /listings` - stability improvements when aggregating fields that contain comma-separated values

May 7, 2026
* `GET /listings` - stability improvements on buildings lookup

May 5, 2026
* `POST /nlp` - now supports  `locationSource` field, supported values: `MLS | UserDefined | LiveBy`

Apr 21, 2026
* `POST /nlp` - better support of enumerated fields
* `GET /locations` - now supports `propertyType=school` along with school specific params `schoolType` , `schoolLevel`,`privateSchoolAffiliation`,`schoolDistrictName`
* `GET /locations` - add support for `name` param allowing exact match filtering of locations by name
* `GET /offices` - fixes
* `GET /listings` - stability fixes

Apr 10, 2026
* `POST /estimates` - V3 of the AI-Estimates model is now used by default
* `GET /offices` - now support filtering by `officeId`
* `GET /brokerages` - fixed filtering by `boardId` for API keys that have access to multiple boards

Apr 7, 2026
* `GET /buildings` - multiple performance improvements

Apr 6, 2026
* `GET /locations` - got new parameter `pointWithinBoundary`.  When set to `true`, returns only locations whose boundaries contain the point specified by `lat` and `long` parameters.

Apr 2, 2026
* `POST /nlp` - got new parameter `useLocationId`.  When set to `true`, any locations identified in the prompt will be returned as `locationId` values instead of being split into separate `area`, `city`, and `neighborhood` parameters.

Mar 31, 2026
* `POST /nlp` - multiple improvements for enumerated fields like `details.swimming`, `details.balcony` etc.

Mar 26, 2026
* `POST /locations` - performance improvements

Mar 17, 2026
* `POST /nlp` now can find coordinates of Points of Interests/Landmarks
* `POST /nlp` now can find coordinates of Major Intersections
* `GET /locations` add support for new Locations `source=LiveBy` and got new `type` values to support locations provided by LiveBy
* `GET /buildings` now returns MLS board prefix inside `image` field

Mar 16, 2026
* `POST /nlp` now works better with locations having same names but located in different regions
* `POST /nlp` got improved treatment of swimmingPool field

Mar 04, 2026
* `POST /nlp` now works better styles in select boards

Feb 27, 2026
* `GET /locations` - add `minSize`, `maxSize` parameters to filter by area size (in square kilometers)
* `GET /locations/autocomplete` - add support for multiple location `source` values, new `type` values, `minSize`, `maxSize` parameters to filter by area size
* `location` objects with boundaries got `size` field representing area size in in square kilometers

Feb 26, 2026
* `GET /listings` - fix `minSoldDate/maxSoldDate` behaviour with `standardStatus` filter
* `GET /listings` - now fetches listings for `locationId` without specifying `locationSource`

Feb 19, 2026
* `GET /listings` - `map` param now supports geo-json MultiPolygon geometry type
* `GET /listings` - got new parameters - `minBathroomsHalf` and `maxBathroomsHalf` - check [API ](https://docs.repliers.io/reference/getting-started-with-your-api)Docs for more details
* `GET /locations` - now supports multiple location `source` values, new `type` values
* `POST /messages` - performance improvements

Feb 6, 2026
* `GET /listings/history` - now returns `address.state` field

Feb 4, 2026
* `GET /listings/` - ensured stability of sorting results

Jan 29, 2026
* `GET /listings` - got new parameters `minClosedDate` and `maxClosedDate` to find listings by `closedDate`

Jan 19, 2026
* `POST /searches` - got some performance improvements
* `GET /listings/history` - zip code fixes

Jan 16, 2026
* `GET /listings/history` - surfaced `permissions` object for each listing inside history
* `GET /listings` - in certain cases `comparables` will now feature `permissions` object
* `POST /searches` - got some performance improvements

Jan 9, 2026
* `GET /listings` - a bunch of stability and performance improvements

Dec 19, 2025
* `POST /estimates` - improvements to [AI-Powered Property Estimates](https://help.repliers.com/en/article/ai-powered-property-estimates-explained-1g0v39s/) model leading to higher quality estimates

Dec 11, 2025
* `GET /listings` - now supports `class = ResidentialProperty | CondoProperty | CommercialProperty` for backward compatibility
* `GET /listings` - now reliably computes `standardStatus` for a listing even for non-compliant boards.
* `GET /listings/history` - got 2 new params: `mlsNumber` & `addressKey`

Dec 2, 2025
* `GET /members` - got new request params allowing more comprehensive member search - `agentName`, `agentId`, `brokerage` . See more details in the [endpoint documentation](https://docs.repliers.io/reference/members#/).

Nov 24, 2025
* `GET /listings` - `contains:` and `notContains:` prefix operators now works with `operator=and:<field_name>` and `operator=or:<field_name>` to change filter application logic
* `GET /listings` improved params validations

Nov 19, 2025
* `GET /listings` improved params validations

Nov 14, 2025
* `GET /listings` improved handling of non-standard-compliant values for [RESO](https://ddwiki.reso.org/display/DDW20/StandardStatus+Lookups) `standardStatus` field
* `GET /listings` fixed handling of [prefix operators](https://help.repliers.com/en/article/using-contains-and-notcontains-prefixes-in-api-filters-c2nga9/) in conjunction with with [AI-Image Search](https://help.repliers.com/en/article/ai-image-search-implementation-guide-mx30ji/)

Nov 13, 2025
* `POST /nlp` multiple improvements to Repliers NLP model v3

Nov 10, 2025
* `GET /listings` - `contains:` and `notContains:` prefix operators now [work for raw fields](https://help.repliers.com/en/article/raw-mls-data-access-with-repliers-nhlg5o/#2-advanced-filtering-with-query-operators) same way as for standard fields
* `GET /listings` - got new `aggregatesUnique` field which will come handy with [containment operators](https://help.repliers.com/en/article/using-contains-and-notcontains-prefixes-in-api-filters-c2nga9/?bust=1760918097610) and [negation operators](https://help.repliers.com/en/article/using-the-not-prefix-in-api-filters-aa38jg/) (more docs on `aggregatesUnique` coming soon)
* `GET /locations/autocomplete` - improved error handling

Nov 4, 2025
* `GET /listings` - `contains:` and `notContains:` prefix operators now [work for all standard fields](https://help.repliers.com/en/article/using-contains-and-notcontains-prefixes-in-api-filters-c2nga9/?bust=1760918097610) and doesn't require composite fields as before.
* `POST /webhooks` got improved validations

Nov 4, 2025
* `POST /nlp` version 3 now detects prompts not related to listings search
* `POST /nlp` version 3 now returns an array of locations identified within the NLP prompt
* `GET /nlp/chats` added endpoint that returns a list of chat sessions
* `GET /nlp` got minor updates
\*

Oct 30, 2025
* `POST /nlp` version 3 of Repliers NLP model released

Oct 27, 2025
* `GET /locations` & `GET /locations/autocomplete` now support `state` parameter
* `POST /nlp` various improvements around NLP model version control

Oct 23, 2025
* `GET /locations` & `GET /locations/autocomplete` now support `hasBoundary` parameter to filter locations that has boundary polygon available (`map.boundary`)

Oct 19, 2025
* `GET /listings` - added support for `contains:` and `notContains:` prefix operators that allow you to filter properties based on specific values within [composite fields (comma-separated strings or arrays)](https://help.repliers.com/en/article/using-contains-and-notcontains-prefixes-in-api-filters-c2nga9/?bust=1760918097610)
* `GET /listings` - added `not:` prefix operator that allows you to [exclude specific values from your search results](https://help.repliers.com/en/article/using-the-not-prefix-in-api-filters-aa38jg/)

Oct 19, 2025
* `POST /nlp` -  updated to accept `nlpVersion` param. V2 of Repliers NLP released
* API Server performance updates

Oct 14, 2025
* `GET /listings` - improvements to [Smart Rules](https://help.repliers.com/en/article/smart-rules-implementation-guide-cbmzaw/) amenities field handling
* `GET /listings` - [CoverImage](https://help.repliers.com/en/article/changing-the-cover-image-of-property-listings-with-ai-powered-coverimage-parameter-40861n/) fix - listings without selected coverImage value are not filtered out

Oct 06, 2025:
* API server speed improvements

Sep 30, 2025:
* check referring domain for [client-side requests](https://help.repliers.com/en/article/client-side-api-keys-developer-guide-11b1t5s/)
* allow `GET /locations` endpoint group for [client side keys](https://help.repliers.com/en/article/client-side-api-keys-developer-guide-11b1t5s/)
* various internal features

Sep 18, 2025:
* GET /listings - not:brokerage operator fix

Sep 16, 2025:
* search speed improvements

Sep 15, 2025:
* GET /listings - now supports [Bundled Searches](https://help.repliers.com/en/article/bundled-searches-developer-guide-17x7tsa/)
* GET /listings - new search params added: `minLotWidth/maxLotWidth` and `minLotDepth/maxLotDepth`

Sep 12, 2025:
* GET /listings - minor stability fixes
* GET /favorites - minor stability fixes

Sep 11, 2025:
* GET /members - support originatingSystemName in trestle members proxy
* POST /listings - [imageSearchItems](https://help.repliers.com/en/article/ai-image-search-implementation-guide-mx30ji/) stability improvements

Sep 08, 2025:
* various internal features

Aug 28, 2025:
* GET /listings - Add minDaysOnMarket/maxDaysOnMarket search fields for status=U listings
* GET /listings - various fixes
* GET /listings/:mlsNumber/similar - dateLimit fixes

Aug 21, 2025:
* Improve Account configurations

Aug 19, 2025:
* GET /listings - fix image search for certain account types

Aug 13, 2025:
* GET /listings - agent email address redaction for certain boards
* improvements to rate-limiter

Aug 13, 2025:
* logging infra improvements
* 500 error fixes

Aug 06, 2025:
* GET /listings - status/lastStatus/standardStatus params validation improvements
* POST /estimates - fixed automatic retries to downstream model
* GET /listings - added tests

Jul 31, 2025:
* GET /listings - Account config extended to have allFields option

Jul 30, 2025:
* GET /listings - Price change computing, logging and filtering
* GET /listings - added priceChangeLog array to listings
* GET /listings - price change filters - maxPriceChangeDateTime, minPriceChangeDateTime, lastPriceChangeType

Jul 30, 2025:
* GET /listings - Fixed Smart Rules with amenities parameter

Jul 29, 2025:
* POST /estimates - AI Model moved to serverless environment

Jul 23 2025:
* GET /listings - fixed parsePrefixedValues
* GET /listings - fixed maxLotSizeSqft

Jul 18 2025:
* GET /listings - added amenitiesOperator (default AND)
* GET /listings - searchFields improvements
* GET /listings - Support maxParkingSpaces
* GET /listings - exclusion for address.streetDirectionPrefix

# What questions does this article answer?

* What recent changes have been made to the Repliers API server?
* Have there been updates to `/listings` behavior, parameter validation, or operators?
* When were specific fixes or enhancements deployed (dates / versions)?
* Where can I check if an observed behavior change is due to a new release?
* How do I keep my integration aligned with ongoing API changes?