# Upcoming changes to modernize search REST APIs **URL:** \ **Category:** Confluence Cloud Announcements\ **Created:** [February 3, 2020, 5:00am UTC](https://community.developer.atlassian.com/t/upcoming-changes-to-modernize-search-rest-apis/37746 "2020-02-03T05:00:00Z")\ **Posts on this page:** 1\ **Showing post:** 26
**Author:** ![BobBergman](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/bobbergman/32/38962_2.png) [@BobBergman](https://community.developer.atlassian.com/u/BobBergman)\ **Post date:** [July 22, 2020, 3:05pm UTC](https://community.developer.atlassian.com/t/upcoming-changes-to-modernize-search-rest-apis/37746/26 "2020-07-22T15:05:22Z")
I have done a but more research this morning and found that the primary difference I can identify is that the value of `results[].content.title` have changed on the EAP release to include the `@@@(end)?hl@@@` values when they do not in production. Looking at the [Confluence Server REST API docs](https://docs.atlassian.com/ConfluenceServer/rest/7.6.1/#api/search-search) I see that there is an `excerpt` query param that accepts a value of `none` but defaults to a value of `highlight`. This query param is **not** documented in the [Confluence Cloud REST API docs](https://developer.atlassian.com/cloud/confluence/rest/api-group-search/). Adding `excerpt=none` to the search query URL in Cloud _does_ seem to revert the API to its current production behavior of not including these highlight annotations in the search result content titles. In production, the `excerpt=none` flag also works to suppress the annotations in `results[].title` field, and the default appears to be `excerpt=highlight`. So the behavioral change that appears to be happening now in the new search API in the EAP is that the `results[].content.title` now respond to `excerpt=*` values, when previously they did not. While easy to work around now that I reverse engineered the secret sauce, this looks to me like a _backward-incompatible behavioral change on the EAP_, and should be **reverted** before shipping to avoid breaking unsuspecting apps and API consumers. Please Atlassian, respond before the July 24th rollout date so we can properly set our expectations as to whether or not you plan to fix this. In any case, _please document the existence, effect and behavior of the secret `excerpt` query param in the search API docs_. I’m not exactly sure why the AtlassianLabs Tree Search app is broken with the EAP search API, but am not going to dig into that any further myself. --- _[View the full topic](https://community.developer.atlassian.com/t/upcoming-changes-to-modernize-search-rest-apis/37746)._