API Management Release Notes for November 2026
API Control Plane
New Feature
-
Added the ability to configure API key rotation policies globally, or at the API product or organization level for Boomi API and Apigee gateways. You can view key validity, expiration dates, upcoming rotations, and trigger manual rotations when needed. Subscribers can see their key status in the developer portal. (ACP-4146)
Refer to API Key Rotation Configuration for more information.
Enhancements
-
Added visibility into MCP server documentation sync status. You can now check sync status directly in the UI, so you know if your documentation needs attention. (ACP-5080)
Refer to MCP Registry Server Catalog for more information.
-
Enabled administrators to hide, reorder, or display options in the developer portal account menu. Previously, these options were displayed by default and could not be changed. To enable this via API, added
GETandPUTendpoints at/devPortals/{id}/menuItems. (ACP-5102)Refer to Developer Portal Details for more information.
-
Added the current organization name to the developer portal header for logged-in users. (ACP-5099)
Fix
- Resolved an issue on the MCP server detail page where the API Product link could point to the wrong product or fail silently, depending on the order of server remotes. (ACP-5216)
API Gateway
New Feature
-
Added TLSv1.3 support for all outbound requests, so the API Gateway can connect to backend services and other endpoints that require TLSv1.3. (APIM-20327)
Refer to
com.boomi.container.httpsProtocolsproperty details in Container properties.
Enhancement
-
Updated the Cache policy to support cache key configuration using request content. In addition to request headers and request parameters, you can now reference the request body/content in the cache key. This enables caching for APIs that pass query and retrieval parameters in the request payload. (APIM-20708)
Refer to Cache policy for more information.
Fixes
-
The API Gateway now normalizes incoming request paths before routing to ensure each request reaches the intended API. The Gateway automatically resolves relative dot segments (
.and..) within incoming URIs before route matching and request forwarding. (APIM-20736) -
Resolved an issue where changing a Gateway's external URL did not update the OpenAPI documentation for APIs deployed on that Gateway. The documentation now shows the updated host, without requiring a redeploy. (APIM-20155)
-
Resolved an issue where IP Filtering request and response spans showed “Missing parent” errors in traces. Spans now stay nested when a backend call times out or returns an error. (APIM-20415)
-
Resolved an issue where a long-running request in progress during an API change could freeze configuration sync across the Gateway node, delaying other API and plan deployments on that node. Configuration sync now continues while the affected API finishes its in-flight requests. (APIM-20603)
Refer to
com.boomi.container.apigateway.api.pendingRequestsTimeoutproperty details in Container properties.