Skip to main content
Feedback

API Management Release Notes for October 2026

Updated 

October 24 2026

API Control Plane

New Feature

  • You can now configure Developer Portal visibility at the API Product level. This allows you to have multiple developer portals with different visibility configurations, regardless of their organization. (ACP-4553)

    Refer to API Product Visibility for more information.

  • API documentation for the MCP Registry is now available on Developer.boomi.com.

Enhancements

  • The Admin role was renamed to Organization Admin. (ACP-4253)

    Refer to User Configuration for more information.

Fixes

  • You could not download the ruleset file. (ACP-5242)
  • A developer portal intermittently rendered different logo images when the authentication page was refreshed. (ACP-5265)

October 13 2026

Cloud API Management

Deferred

The Cloud API Management release originally scheduled for October 13, 2026 has been deferred to a future release. The features, enhancements, and fixes listed below are not currently available.

New Feature

  • Introduced Policy Templates in Cloud API Management to help you keep policy configuration consistent across endpoints. Previously, you had to configure pre-processing and post-processing policies separately for each endpoint. Now you can define a set of pre-processing and post-processing policies once in the template and reuse the same configuration across multiple endpoints. (WA-17789)

    You can create policy templates from Manage > Policy Templates. From the Endpoint Policies page, you can attach a template to as many endpoints as you need, and override it for a specific endpoint without changing the original template.

Enhancement

  • SAML-based single sign-on (SSO) for Cloud API Management Control Center and Developer Portal now uses stronger signing and stricter SAML response validation by default. This change applies to all existing and new environments. Setting up SSO with your own identity provider now requires a private signing key and a valid public certificate, which you provide through a support request. Existing SSO integrations require no action. (WA-17925)

Known Issues

This issues will be fixed in an upcoming release:

  • The Circuit Breaker policy is not recognized as a chaining policy in Cloud API Management. As a result, Control Center does not apply the one-chaining-policy limit to it. If a chaining policy, such as the OAuth2 JWT Authentication policy, is already added, you can still add the Circuit Breaker policy without an error. This applies to both configuration methods (WA-18616):

    • Multiple endpoints: When you create a template on the Policy Templates page, attach templates on the Endpoint Policies page, or override an attached template on the Endpoint Policies page.
    • Individual endpoint: On the Call Transformations page, when you configure policies directly on an endpoint.

    Workaround: Add only one chaining policy per template or endpoint when you create a template on the Policy Templates page, attach, or override a template on the Endpoint Policies page, or add policies on the Call Transformations page.

  • When multiple policy templates attached to an endpoint on the Endpoint Policies page contain the same policy, Traffic Manager runs only the first one, based on attachment order. It ignores the others, so any configuration values that differ from the first do not take effect. (EIN-24920)

October 3 2026

API Gateway

Fix

  • Policy Rule and Policy Template paths now preserve their exact typed casing upon save instead of converting to lowercase (APIM-20606).
    Note: This fix applies to new saves going forward. Existing paths that users created while the defect was active remain stored in lowercase; users must detach and reattach those policies with the correct casing to update them.
On this Page