API Management (Sensedia Platform)

We fixed the display of the response log in the log interceptor, which was not shown in JSON format.

We fixed a failure in API deployments with the XSS Threat Protection interceptor, which returned a bad request error.

We fixed an issue where the XSS Threat Protection interceptor duplicated records when adding or removing fields, preventing the duplicated value from being removed.

We fixed the display of logs generated by the log interceptor in Trace, which appeared blank without the request and response data.

We fixed an issue where edits to a plan’s CustomJS were not reflected in the API Trace. The Trace continued to show the previous CustomJS value even after the change was saved.

On the Manager API listing screen, you can now open an API’s details directly in a new browser tab using right-click and "Open in new tab", Ctrl+click, or the middle mouse button. The API list tab remains open without redirection, making it easier to compare configurations, review deployments, or perform troubleshooting in parallel.

We fixed an issue where the General Trace date filter ignored the time zone configured in the user’s profile. When selecting a date range in the calendar, requests were always sent using the UTC offset, causing the displayed traces to appear several hours apart from the selected period.

We fixed an issue where certain requests to Connector Manager returned error messages with more information than expected. Error responses are now standardized, and technical details are restricted to internal logs.

Prompts written in English generate 100% English contracts (e.g., /accounts, /transactions).

Prompts written in Spanish generate 100% Spanish contracts (e.g., /cuentas, /transacciones).

The feature can be used in demonstrations and international scenarios without requiring additional adaptations.

We fixed an issue in AI Copilot where, when deleting a journey during API creation via the Journey option, the form reset all previously configured settings and returned to the initial screen of the flow, instead of continuing normally with the remaining journeys.

We fixed an issue where the search filter on the Access Tokens screen returned a 500 error when searching for or opening a token from the actions column.

We fixed an issue where the dates displayed in General Trace did not match the period selected in the filter.

We have modernized the screens for the Overview and API Editing flows. They now feature a new look and a more advanced front-end technology, while fully preserving API functionality and providing a smoother, more consistent, and more productive navigation experience for daily use.

We fixed a bug that prevented the display of available maps when using the Import Map option during the creation or editing of environments, making it impossible to import previously configured settings.

We fixed security issues identified in the platform modules (agent-authorization, agent-gateway, api-authorization, api-gateway, and logstash-federated). The fixes include internal component updates.

We implemented an evolution in the Environments update flow, especially focused on scenarios with a large volume of routes and variables. The improvement delivered significant performance gains, including:

We fixed a bug that prevented selecting the HTTP method in the Service Callout interceptor configuration when adding it to a plan flow.

We fixed a bug that caused an error when trying to delete a configuration on the Console > System Config screen. Now, it is possible to delete configurations normally.

2025

2024

2023