API Management (Sensedia Platform)

Fixed vulnerabilities in the base image and in the dependencies of the logstash-hybrid-http (v5.0.1.0) and logstash-hybrid-kafka (v5.3.0.0) services.

Fixed an issue where the original request headers (such as Authorization) were not propagated to the internal call made by the Service Callout interceptor with the Preserve Header option enabled. Now, the headers are correctly forwarded to the second API triggered in the flow.

Fixed an issue where the deployment of an API was interrupted with a bad request error when using the Destination interceptor in APP format with a variable configured in the application. Now, even if the destination address is not fully configured, the API deployment flow is maintained, and the interceptor routes the request normally according to the available configurations.

Fixed an issue where, when creating or editing an API through the screen, saving a resource with simultaneous clicks or submissions (double-click, double-submit, or slow network) could generate duplicate routes. Now, concurrent saves of the same revision no longer generate duplicate resources, and the API is created with the correct routes, without requiring manual editing to remove duplicates.

Removed a behavior where, when deleting a legacy interceptor in Edit API > Flow, an empty icon remained on the screen. Now, only active interceptors remain visible.

Attribute values in API Catalog are now displayed correctly when Adaptive Governance is enabled.

Interceptors organized under custom tags are again displayed correctly when editing routes, even when there are tags with the same name as default categories.

Fixed an issue with token generation from a newly created application (APP).

Fixed an issue when publishing an API Swagger.

Fixed an inconsistency caused by Log Obfuscation when editing an API.

Fixed an issue when updating an API in production.

Fixed an issue when deleting APIs.

Fixed an issue where Internal API Call did not forward query parameters to the destination API.

Fixed an issue where Set API Destination was not updated.

Fixed an issue where the Cancel action did not work correctly in interceptors.

Fixed an issue where interceptors were not displayed.

Fixed an issue with log filtering in Trace.

Fixed issues when importing WSDL contracts.

Fixed an issue where Environment variables disappeared after a period of time.

Fixed an issue where the Service Callout interceptor did not accept variables in the URL field.

Fixed an issue that prevented removing the owner from an API.

Fixed URL copying in the new API Design screen while in edit mode.

Fixed inconsistent behavior when creating operations through Connector.

Fixed duplicate Flow interceptors when saving changes while editing an API Swagger with Adaptive Governance enabled.

Fixed an issue where the button became inaccessible on the Import Existing Map screen when the Environment contained a large number of variables.

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