API Management Release Notes for November 2026

Updated 30 October 2026

Documentation sync status is displayed when you create, update, or delete MCP server documentation. You can see a notification confirming success or alerting you to a failure, so you always know whether your documentation is current. (ACP-5080)
Users that are logged into the developer portal can now see their current organization name displayed in the developer portal header. (ACP-5099)
The options in the developer portal account menu can be hidden, reordered, or displayed by an administrator user. Previously, these options were displayed by default and could not be changed. (ACP-5102)

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)

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)
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)

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)
Fixed a defect 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)

Platform Release