federated-searchesendpoints) and the attribute used is not marked for use as a filter or for sorting, an error is returned.
Fixed: Dynamic abstracts generated for each result were not generated considering the selected user type. This means that the dynamic abstract may have displayed information from an unintended user type. It is fixed now, and it only displays the content attribute value of the requested user type.
Added: We added
score as one of the options available in our API to sort contents. It allows sorting contents by the matching score returned for a given query. It can help to create custom sorting logics when different results have the same score. Find more information here.
Added: To increase the security in our system, we removed the Set-cookie header returned from the API.
Fixed: Search API must split the user query internally when it is longer than 255 characters. This was not working for all cases, causing delays in processing some user queries.
/federated-searchesendpoints, the API returned a 500 error. This is now fixed.
Updated: We updated Inbenta rate-limits.
From now on, the Search API endpoints
/federated-searches responses will provide two new parameters for each result found: creationDate and modificationDate. These parameters represent the date when the content was first indexed and last modified, respectively.
/federated-searchesendpoints to limit the number of results, if the splitQuery was set to true, the API could return more results than maxResults. This is no longer the case.
x-inbenta-envin API requests is set as "development", the request will point to fromsite "Internal test" in the Search App.
/federated-searchin instant answers takes from 2 to 4 seconds
Fixed: Filters containing ":" were not parsing correctly. They do now.