Skip to main content
Feedback

API Management September 2025 Release Notes

September 23 2025

Cloud API Management

New
We added this feature

  • You can now set a custom timeout value for an endpoint in the Time to wait for a response from endpoint field on the Endpoint Settings page (API Definitions > Endpoints > More Settings). The timeout value entered should be between 2 and 1200 seconds.

    A timeout value less than or equal to 60 seconds can be set directly in the Boomi Cloud API Management. Any value greater than 60 seconds requires assistance from Boomi via a support case. This limitation is only applicable to Boomi Cloud API Management and does not apply to Boomi Cloud API Management - Local Edition. (WA-13773)

    Refer to Configuring Endpoint More Settings for more information.

Fix
We fixed these issues

  • All known issues within Call Inspector from the previous release have been fixed in this release. (WA-16152)

  • Previously, administrators could create a new package key for inactive users in the Boomi Cloud API Management area. Ideally, administrators should not be able to assign a package key to users whose status shows Disabled on the Users page (Manage > Users).

    This issue is now fixed. If an administrator tries to create a new package key for a disabled or inactive user, they will receive a warning message to enable the user account first, then assign the new package key. (WA-16382)

    Refer to Creating Package Keys for more information.

  • When creating an endpoint with the V3 API, you must include a forward slash / before the outboundRequestTargetPath value (for example, “outboundRequestTargetPath”: “/endpoint”). If you do not include a forward slash /, you should see an error message. Previously, no error message was displayed when a V3 API endpoint was created without a forward slash /. This issue has now been fixed. Now, a 504 Gateway Timeout error message is displayed when a forward slash / is missing in the outboundRequestTargetPath value. (WA-16411)

September 20 2025

API Gateway

Fix
We fixed this issue
  • WSS web service listener processes in API service components now deploy and undeploy without errors. You can deploy both existing and new packages successfully, and enable or disable the API Lifecycle feature without any impact. (APIM-18389)

Platform Release

September 13 2025

API Control Plane

New
We added these features

  • The Send to Boomi Integration feature streamlines the implementation of APIs with Boomi Integration. You can design or import an OpenAPI specification file and send it from API Control Plane to Boomi Integration with one click, where it creates an API Service component with input/output profiles and process stubs for each defined operation. An integration developer can use these stubs to quickly implement the API logic and connectivity. (ACP-1514)

    Refer to Send to Boomi Integration for more information.

  • Apigee X and Apigee Hybrid APIs, products, plans, and applications can be discovered and managed in API Control Plane. (ACP-1245)

    Refer to How to Connect to Apigee for more information.

  • API Control Plane can now expose managed API Products via Model Context Protocol (MCP) for use as AI Agent tools. This feature is currently in Tech Preview. (ACP-1343)

    Refer to MCP in API Control Plane for more information.

  • You can now import 3.1 OpenAPI specification files.

    note

    The whole 3.1 schema is not supported. See troubleshooting and known limitations for more information.

    note

    Upcoming Retirement Notice: In the November 2025 release, all entities in API Control Plane will consume and return UUIDs instead of integer IDs. Integer IDs will be accepted for incoming requests, but all responses will only contain the UUID. Integer IDs will be fully retired in early 2026.

Fix
We fixed this issue
  • Duplicate API products were being discovered if there were different environments with the same APIs. (ACP-1663)

API Gateway

New
We added this feature

  • API Gateway now supports OpenTelemetry to collect and export telemetry data to improve observability and monitoring of API performance and facilitate troubleshooting. (APIM-17663)

    Refer to OpenTelemetry support for more information.

Fix
We fixed these issues

  • Fixed file handle leaks in the Boomi Gateway runtime, preventing the accumulation of open file descriptors that previously required restarting the node. (APIM-17746)

  • Improved deployment time for API Service components by optimizing the calculation of API Interface versions, reducing the need to load the latest component and check the branch. This change enables faster and more efficient deployments. (APIM-18074)

  • Fixed the single date filter in the API Management (APIM) dashboard, enabling users to accurately view data for a specific date. (APIM-17851)

On this Page