---
schema_version: "1"
id: ff27bbb3bd5cc5f2f4a7b80d6482f9f20396443e49822e3a7a5a000876af88a2
title: API Manager 2.x Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/api-manager/api-manager-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/api-manager/api-manager-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: f2a5db1c098016b980ed988a704646277f0c56749cb07f58d304aa30cdb9a684
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
keywords: release notes, apis, anypoint platform for apis, anypoint platform
---

# API Manager 2.x Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

API Manager release notes include information about changes, new features, improvements, and
resolved issues in releases of API Manager.

## 2.5.32

**October 21, 2026**

### What’s New

- API Manager now supports creating API instances from OAS 3.1 API specifications for Mule Gateway
  and applying policies to them.  
  For more information, see [OpenAPI Specification Support Release Notes](https://docs.mulesoft.com/release-notes/platform/oas3).
  **October 19, 2026**

### What’s New

- API Manager now supports enabling different versions of the same policy on a single API instance.

- Sensitive fields are now redacted from audit log entries for policy operations (enable, disable,
  edit, and create).

- Managed Gateways now support configuring OpenTelemetry log output and selecting a custom tracing
  provider.

- The key metrics panel in API Manager now links to the Anypoint Monitoring page in the enhanced
  experience.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Contract creation no longer fails when an API has more than 100 tiers.</p></div></div></td><td><div><div><p>W-19808895</p></div></div></td></tr><tr><td><div><div><p>Public API instances are now displayed correctly in the public portal.</p></div></div></td><td><div><div><p>W-21151907</p></div></div></td></tr><tr><td><div><div><p>Users with API Manager permissions (API Creator, View APIs Configuration, Edit APIs Configuration, or Manage Policies) can now create and manage LLM proxies without requiring the Organization Administrator role. Model names now display correctly in Model Wallets and Model Proxies for these users.</p></div></div></td><td><div><div><p>W-24194029</p></div></div></td></tr></tbody></table>

## 2.5.31

**August 13, 2026**

### What’s New

- The model proxy now uses the embedding provider from the selected Semantic Service configuration
  when creating prompt topics.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Mule proxies deployed to CloudHub 2.0 private spaces now preserve the customer-defined ingress configuration.</p></div></div></td><td><div><div><p>W-21464257</p></div></div></td></tr></tbody></table>

## 2.5.30

**May 14, 2026**

### What’s New

- API Manager now includes a DataWeave expression validator in policy configurations, helping you
  identify and avoid common errors when writing expressions.

- The model proxy now supports advanced semantic routing using vector database providers, enabling
  intent-based routing of LLM requests to the appropriate model.

- The model proxy now supports the Nvidia Nemotron model.

- OAuth configuration in the model proxy now supports DataWeave expressions for dynamically
  retrieving client LLM provider keys.

- The model proxy monitoring dashboard now shows token usage broken down per LLM provider.

- The MCP Bridge now supports updating existing MCP Bridge servers.

## 2.5.29

**April 20, 2026**

### What’s New

- API Manager now supports agent verification using GoDaddy Agent Name Service (ANS), enabling you
  to validate domain ownership and establish a trusted identity for your agents.  
  To learn more, see
  [Register Agents with GoDaddy ANS](https://docs.mulesoft.com/api-manager/latest/godaddy-ans-registration).

## 2.5.28

**March 30, 2026**

### What’s New

- API Manager now supports model proxies, allowing you to manage and govern interactions with
  multiple large language models (LLMs) providers through API Manager.

  To learn more, see [Creating and Managing Model Proxies](https://docs.mulesoft.com/general/model-proxy).

## 2.5.27

**March 16, 2026**

### What’s New

- API Manager now supports managing gRPC APIs as API instances when the API is published as a gRPC
  asset in Anypoint Exchange and deployed using Omni Gateway.

## 2.5.26

**March 6, 2026**

- API Manager now supports creating an MCP Bridge to expose API instances as an MCP server.

  See [Adding an MCP Bridge Instance](https://docs.mulesoft.com/api-manager/latest/create-instance-task-mcp-bridge).

## 2.5.25

**February 13, 2026**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Mule proxies deployed to CloudHub 2.0 private spaces from API Manager no longer have the public endpoint disabled by default.</p></div></div></td><td><div><div><p>W-17293229</p></div></div></td></tr></tbody></table>

## 2.5.24

**January 23, 2026**

### What’s New

- You can now create and manage instances for publicly available MCP servers in API Manager. These
  assets are published to Exchange under Provided by MuleSoft and are maintained by their original
  providers, not by MuleSoft.  
  When you create an instance from a publicly available asset, the instance is created within your
  private organization and managed like any other instance in API Manager.

For more information, see
[Adding an MCP Server Instance from Public Exchange](https://docs.mulesoft.com/api-manager/latest/create-instance-public-exchange).

## 2.5.23

**December 17, 2025**

### What’s New

- You can now import client applications from Okta client providers into API Manager and use them to
  request access to API instances.  
  For details, see
  [Import Client Applications from Client Providers](https://docs.mulesoft.com/api-manager/latest/import-client-applications).

## 2.5.22

**December 11, 2025**

### What’s New

- You can now configure the same API-level or automated policy more than once on a single API
  instance.  
  For details, see
  [Apply Duplicate Policies](https://docs.mulesoft.com/gateway/latest/policies-reorder#apply-duplicate-policies).

- Policy templates now support an optional `assetTypes` field in their capabilities (`http`, `rest`,
  `wsdl`, `a2a`, `mcp`, `llm`, `grpc`).  
  When this field is defined, the policy can only be applied to assets whose endpoint type matches
  one of the specified values.

- Automated policies now support an optional `endpointTypes` field in their application rule.  
  If the associated policy template defines `assetTypes`, the `endpointTypes` value must be a subset
  of those asset types. Automated policies apply only to assets whose endpoint type is included.

## 2.5.21

**November 10, 2025**

### What’s New

- API Manager now prevents applying deprecated policy template versions from Exchange and clearly
  flags existing policies that use deprecated versions.

## 2.5.20

**October 3, 2025**

### What’s New

- API Manager now supports managing brokers, MCP servers, LLMs, and agents.

- TLS 1.0 and 1.1 support is removed for enhanced security compliance.

## 2.5.19

**October 1, 2025**

### What’s New

- You can now filter the API list by endpoint type.

- You can now select API assets from other business groups you have access to when creating new
  instances.

## 2.5.18

**September 22, 2025**

### What’s New

- API Manager now includes comprehensive entity limits documentation, providing clear information
  about API policies, groups, SLA tiers, and automated policy configurations.

See [API Manager Entity Limits](https://docs.mulesoft.com/api-manager/latest/limits#api-manager-entity-limits).

## 2.5.17

**September 4, 2025**

### What’s New

- API Manager now includes a link to test DataWeave expressions in the Anypoint DataWeave Playground
  when configuring policies.

- This release contains accessibility improvements in the UI.

## 2.5.16

**July 25, 2025**

### What’s New

- API Manager now allows requiring manual approval when adding an API instance.

- Resource Level Policies for Omni Gateway now support case-insensitive URI patterns using the
  `(?i)` flag, allowing regex-based policies to match URIs regardless of letter casing.

## 2.5.15

**June 27, 2025**

### What’s New

- API Manager now supports publishing an Omni Gateway SOAP API instance by uploading a WSDL file for
  your SOAP API.

See [Adding an Omni Gateway API Instance](https://docs.mulesoft.com/api-manager/latest/create-instance-task-flex).

## 2.5.14

**June 3, 2025**

### What’s New

- Mule API Analytics is now replaced by [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/). Use Anypoint
  Monitoring to monitor APIs effectively.  
  Contact your MuleSoft representative for more information.

## 2.5.13

**May 28, 2025**

MuleSoft announces API Manager support for Model Context Protocol (MCP) and Agent2Agent (A2A)
Protocol through Omni Gateway.

### What’s New

- API Manager now supports publishing Omni Gateway MCP and A2A server instances, enabling you to
  secure, manage, and govern agent interactions.

To learn more, see:

- [Omni Gateway Release Notes](https://docs.mulesoft.com/release-notes/gateway/gateway-release-notes)

- [Securing Agent Interactions with Omni Gateway](https://docs.mulesoft.com/gateway/latest/agent-secure)

- [Adding an Omni Gateway Agent or Tool Instance](https://docs.mulesoft.com/api-manager/latest/create-instance-task-agent-tool)

## 2.5.12

**May 15, 2025**

### What’s New

- Automated policies can now be reordered from the Automated Policies configuration page.

- The Upstream Service limits per API is now increased to 100 for Omni Gateway.

## 2.5.11

**April 30, 2025**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Deployments to Flex Gateway no longer fail if users trigger them without secret access permissions.</p></div></div></td><td><div><div><p>W-17566778</p></div></div></td></tr><tr><td><div><div><p>Contract status no longer changes when a team owns the application.</p></div></div></td><td><div><div><p>W-18034262</p></div></div></td></tr><tr><td><div><div><p>You can now access the correct documentation pages from links in the UI.</p></div></div></td><td><div><div><p>W-17865398</p></div></div></td></tr></tbody></table>

## 2.5.10

**February 18, 2025**

### What’s New

- Patch operations to existing API portals are no longer supported. For more information, see se
  [API Experience Hub](https://docs.mulesoft.com/api-experience-hub/).

- Application responses no longer contain unsolicited owner information.

- Flex Gateways now report their status as `Running` or `Not Running` instead of `Connected` or
  `Disconnected`.

- The user owner search UI now includes a username field.

- You can now change policy versions when editing Automated Policies.

## 2.5.9

**November 12, 2024**

### What’s New

- Now, when the first request from a Mule API Gateway to API Manager is performed for a particular
  API, API Manager makes an initial setup with the provided information.  
  NOTE: If additional requests are received for the same API during this setup, the Gateway will
  receive a 429 error status.

- The Service Mesh End Of Life creation blocker is now active.

- Customers without a CloudHub entitlement cannot deploy proxy applications through API Manager.

## 2.5.8

**November 1, 2024**

### What’s New

- Teams can now be client application owners.

## 2.5.7

**October 31, 2024**

### What’s New

- Service Mesh is scheduled for End of Life on May 21, 2025. To integrate your micro services with
  Anypoint Platform, use [Flex Gateway](https://docs.mulesoft.com/gateway/latest/) instead.

## 2.5.6

**October 30, 2024**

### What’s New

- The automated policy list is now shown in order of application.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The API list now shows the correct states for Flex Gateway APIs.</p></div></div></td><td><div><div><p>W-17015895</p></div></div></td></tr></tbody></table>

## 2.5.5

**October 16, 2024**

### What’s New

- You can now view more owners by default on the Client Applications page.

- You can now apply policies to APIs deployed to Flex Gateway, even if the Gateway version is
  unknown (because no replicas are connected).

- You can now see APIs with multiple upstreams in the Project View.

- You can now create self-managed server APIs using the API wizard.

- You now see a notification for API Manager 1.x end of life on organizations that have unclassified
  APIs.

- You can now use both internal and external client providers within the same environment at the
  same time.  
  For more information, see
  [Configure Multiple Client Providers for Client Management](https://docs.mulesoft.com/api-manager/latest/configure-multiple-credential-providers).

## 2.5.4

**October 7, 2024**

### What’s New

- Now, when deploying an API with policies to Flex Gateway for the first time, policy
  implementations are pinned.

- Now, if a user attempts to change the Flex Gateway version where an API is deployed, and one of
  the applied policies is not compatible with the new target, the operation is rejected.

- Now, When changing the Flex Gateway version, if an Automated Policy currently covering the API is
  lost, the user is now warned and can choose to either proceed or cancel the operation.

## 2.5.3

**October 1, 2024**

### What’s New

- You can now see HTTP API instances in Governance reports, as well as AsyncAPI and REST API
  instances.

- API Manager now includes a header `x-request-d` to include the internal trace ID.

- Email URL functionality for contracts generated in API instances within sub-organizations is now
  operational.

- You can now apply different versions of the same policy to various resources within the same API
  instance.

- API instance SLA Tier limits are now validated to ensure that `maximumRequests` and
  `timePeriodInMilliseconds` are integers.

- You can now see the SLA Tier in the client application page for APIs from environments.

- Now, only users with environment or organization credentials are able to export API instances
  policies with sensitive fields.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>You can now see new implementations when using the <strong>Check for implementation updates</strong> button for automated policies.</p></div></div></td><td><div><div><p>W-16619577</p></div></div></td></tr></tbody></table>

## 2.5.2

**August 27, 2024**

### What’s New

- The API Key Metrics experience receives frequent updates. To ensure uninterrupted access, verify
  that [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/) is enabled:

  - CloudHub 2.0 and Runtime Fabric applications: Anypoint Monitoring is enabled by default.

  - CloudHub applications: Configure Anypoint Monitoring. See
    [Setting Up Monitoring for CloudHub Deployments](https://docs.mulesoft.com/monitoring/configure-monitoring-cloudhub).

  - Hybrid Runtime applications: Install the Anypoint Monitoring Agent. See:
    [Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## 2.5.1

**August 23, 2024**

### What’s New

- Mule API Analytics will soon be replaced by [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/). Start
  transitioning to Anypoint Monitoring to monitor APIs effectively. Contact your MuleSoft
  representative for more information.

- Audit logs now include a trace id.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Modifying an API label for a hybrid proxy application now correctly updates the existing proxy application.</p></div></div></td><td><div><div><p>W-15838700</p></div></div></td></tr><tr><td><div><div><p>Users without FlexGateway entitlement are now able to publish split model custom policies.</p></div></div></td><td><div><div><p>W-16496236</p></div></div></td></tr></tbody></table>

## 2.5.0

**July 11, 2024**

### What’s New

The following endpoint responses now include fewer fields, and the responses include no sensitive
information:

- [GET API Instance Contract by ID](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/minor/1.0/console/method/%231674/)

- [GET API Group Instance Contract by ID](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/minor/1.0/console/method/%232394/)

For information about which fields are now included in the responses for these endpoints, see the
[API Manager API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/) documentation.

## 2.4.30

**June 11, 2024**

### What’s New

- API Manager now limits the number of API Groups, API Group Versions, and API Group Instances per
  business group. Each business group can have a maximum of:

  - 1200 API Groups

  - 1200 API Group Versions

  - 2000 API Group Instances

- This release contains accessibility improvements.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Deploying an API proxy for the first time with an old policy implementation version now succeeds (and no longer returns HTTP status code 500).</p></div></div></td><td><div><div><p>W-15945517</p></div></div></td></tr></tbody></table>

## 2.4.29

**May 22, 2024**

### What’s New

- When multiple Mule gateways are connected to the same API instance, API Manager now saves the
  highest gateway version.

- This release contains accessibility improvements, including additional focus indicators and fixes
  for some contrast color issues.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Policy incompatibilities are now calculated each time rather than only when the runtime or java version changes.</p></div></div></td><td><div><div><p>W-15467066</p></div></div></td></tr><tr><td><div><div><p>The correct Java version is now shown when creating Mule APIs.</p></div></div></td><td><div><div><p>W-15578441</p></div></div></td></tr></tbody></table>

## 2.4.28

**April 12, 2024**

### What’s New

The following API Manager permissions are now available in Access Management:

- **Manage Client Applications**: Enables users to create and manage client applications in the root
  organization. Users with this permission can view and modify application credentials and can add
  and remove client owners.

- **View Client Applications**: Enables users to view client applications in the root organization.
  Users with this credential cannot view an application’s secrets and cannot modify applications.

## 2.4.27

**February 29, 2024**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When editing APIs, <strong>Save &amp; Apply</strong> is now disabled for users that don’t have the edit API permissions.</p></div></div></td><td><div><div><p>W-15040213</p></div></div></td></tr><tr><td><div><div><p>When configuring a new hybrid API instance in an environment where only Mule 3 targets are present, you can now select a Mule 3 target.</p></div></div></td><td><div><div><p>W-15102034</p></div></div></td></tr></tbody></table>

## 2.4.26

**February 15, 2024**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When you promote a <strong>Hybrid</strong> API instance to a new environment, the <strong>API Summary</strong> now renders correctly.</p></div></div></td><td><div><div><p>W-15030396</p></div></div></td></tr></tbody></table>

## 2.4.25

**February 7, 2024**

### What’s New

- You can now upgrade your policies and API proxies to Java 17. See
  [Upgrading Policies](https://docs.mulesoft.com/general/java-support#policies) and
  [Upgrading API Proxies](https://docs.mulesoft.com/general/java-support#api-proxies).

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When applying a resource-level policy to specific methods of the API instance, the <strong>URI template regex</strong> field no longer shrinks when you select multiple <strong>Method</strong> values.</p></div></div></td><td><div><div><p>W-14802785</p></div></div></td></tr><tr><td><div><div><p>When you promote a <strong>Hybrid</strong> API instance to a new environment, the API instance classification remains <strong>Hybrid</strong> and is no longer reclassified to <strong>Standalone</strong>.</p></div></div></td><td><div><div><p>W-14829827</p></div></div></td></tr></tbody></table>

## 2.4.24

**January 24, 2024**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When applying an automated policy, the <strong>Rule of application</strong> selection now renders correctly.</p></div></div></td><td><div><div><p>W-14853129</p></div></div></td></tr></tbody></table>

## 2.4.23

**December 6, 2023**

### What’s New

- Resource-level configuration options are no longer shown when applying a policy that does not
  support resource-level configurations.

- The UI is now improved for accessibility by including the addition of alternative text for images,
  and alternative visual and non-visual indicators.

- A warning is now displayed when policies are incompatible with the API runtime version.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>API Manager now properly redirects pre-crowd customers.</p></div></div></td><td><div><div><p>W-13783748</p></div></div></td></tr></tbody></table>

## 2.4.22

**October 27, 2023**

### What’s New

API Manager now supports space selection for Mule API Proxies deployed to CloudHub 2.0.

## 2.4.21

**October 17, 2023**

### What’s New

API Manager now supports Anypoint API Governance conformance reports for governed API instances.

\+ To learn more about governing API instances, see:

\+ **[Anypoint API Governance Release Notes](https://docs.mulesoft.com/release-notes/api-governance/api-governance-release-notes)**
[Governing API Instances](https://docs.mulesoft.com/api-manager/latest/govern-api-instances)

## 2.4.20

**October 10, 2023**

### What’s New

- Mule 4.4.x is now the default version for API proxies deployed to CloudHub, CloudHub 2.0, and
  Runtime Fabric.

- For API instances deployed to CloudHub 2.0, the space name is now visible in the API Settings.

- You can now dismiss Mule 3 end of life notifications for 14 days.

- For API instances deployed to Flex Gateways version 1.5.0 or later, API Manager automatically sets
  the upstream’s **Weight** to 100% and disables the field when only one upstream service exists for
  that route. Adding an additional upstream to the route enables you to configure the upstream
  **Weight**.

- This release contains accessibility improvements in the UI, including the addition of alternative
  text for images and alternative visual and non-visual indicators.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>For Flex Gateway HTTPs API instances sharing the same port, if one of the instances has an inbound TLS context applied, leaving the inbound TLS context blank for additional instances applied to the same port does not result in an error.</p></div></div></td><td><div><div><p>W-14162848</p></div></div></td></tr></tbody></table>

## 2.4.19

**August 23, 2023**

### What’s New

- For requests made from Connected Apps, API Manager Audit logs now include the Connected App’s name
  and ID.

- The **Mule API Analytics** tab is now visible to users with `View APIs Configuration` permission.

- Some error messages are now improved for clarity.

## 2.4.18

**August 7, 2023**

### What’s New

- External **Bad Request** (`400`) errors do not convert to **Bad Gateway** (`502`) errors.

- This release contains accessibility improvements in the UI, including the addition of alternative
  text for images and alternative visual and non-visual indicators.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>You can now apply Mule 4 custom policies uploaded to Exchange via Maven as automated policies in an environment without APIs.</p></div></div></td><td><div><div><p>W-12369588</p></div></div></td></tr></tbody></table>

## 2.4.17

**July 20, 2023**

### What’s New

- API Manager now supports API instances with multiple upstream services for Flex Gateway running in
  Connected Mode.

  For more information, see
  [Multiple Upstream Services for Flex Gateway Running in Connected Mode](https://docs.mulesoft.com/api-manager/latest/create-instance-task-flex#traffic-management).

- Deployments to deprecated Flex Gateway versions are now blocked.

  For information about Flex Gateway version support, see
  [Product Versioning and Back Support Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf)

- This release contains accessibility improvements in the UI, including the addition of alternative
  text for images and alternative visual and non-visual indicators.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Autocomplete for the <strong>Upstream URL</strong> field now works correctly. API Manager now only autocompletes the field when the page is first loaded and only if the information is available.</p></div></div></td><td><div><div><p>W-13735853</p></div></div></td></tr><tr><td><div><div><p>The <strong>Client provider</strong> field now shows the correct provider when editing an API instance.</p></div></div></td><td><div><div><p>W-13768260</p></div></div></td></tr></tbody></table>

## 2.4.16

**July 3, 2023**

### What’s New

- When adding a new API instance, there are now separate pages for the upstream and downstream
  configuration settings.

- When editing an API instance from the settings page, there are now separate sections for the
  upstream and downstream configuration settings.

## 2.4.15

**June 6, 2023**

### What’s New

- Selecting an API instance from **API Administration** now navigates you to the new **API Summary**
  page instead of the API **Settings** page. The API **Key Metrics** and the API instance
  information such as the type, API version, and API instance ID now appear on the **API Summary**
  page. Only the runtime and endpoint configuration still appear on the **Settings** page.

- In **API Administration**, the **Analytics** tab is now **Mule API Analytics**.

## 2.4.14

**May 23, 2023**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The API <strong>Instance</strong> field now appears correctly when filtering client applications with Datagraph contracts.</p></div></div></td><td><div><div><p>W-12964876</p></div></div></td></tr></tbody></table>

## 2.4.13

**May 10, 2023**

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>API Manager now correctly shows disabled policies.</p></div></div></td><td><div><div><p>W-13030137</p></div></div></td></tr></tbody></table>

## 2.4.12

**April 14, 2023**

### What’s New

- Connected Apps can create and manage client applications. For more information, see
  [Creating Client Applications with the Connected App Feature](https://docs.mulesoft.com/api-manager/latest/manage-client-apps-connected-apps-concept).

- API status is now shown as active only when deployment is successful.

- API Manager uses a standalone replica list to report configuration status based on the version of
  each connected replica.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When a deployed API instance with policies applied is deleted, the policies are also deleted.</p></div></div></td><td><div><div><p>W-12779232</p></div></div></td></tr></tbody></table>

## 2.4.11

**March 28, 2023**

### What’s New

You can deploy Mule Gateway proxy applications directly to CloudHub 2.0.

### Fixed Issues

When applying policies to non-REST APIs, policies only applicable to REST APIs are not visible.

## 2.4.10

**February 22, 2023**

### What’s New

For Flex Gateway running in Connected Mode, API Manager now supports:

- Policy execution order

  For more information, see [Reordering Policies](https://docs.mulesoft.com/gateway/latest/policies-reorder).

- TLS and mTLS context configuration

  For more information, see
  [Configuring TLS Context for Flex Gateway in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-tls-config).

## 2.4.9

**January 18, 2023**

### What’s New

For API Instances, the **Implementation URI** and **Consumer endpoint** fields now:

- Validate if the specified URL is a valid URL.

- Support parameterization using `{}`, `<>`, or `<<>>`.

## 2.4.8

**November 8, 2022**

### What’s New

Added TLS inbound and outbound support for RTF targets.

## 2.4.7

**November 2, 2022**

### What’s New

The API Header on the settings page is improved for a better experience:

- The API actions are now inside the **Actions** button in the page header title.

- The API header is now only informative. The content in the API header is not editable, and the
  edit buttons were removed. The API instance label and API consumer endpoint fields editable in the
  API header are now only editable in the Endpoint configuration section following the API header.

- For Mule 4 APIs, since the auto-discovery ID is the same as the API instance ID, the
  auto-discovery ID was removed for clarity. The API Manager docs are updated to highlight this
  change and instruct users where to find the API instance ID.

- The API notification messages are now displayed at the beginning of the API header.

## 2.4.6

**October 17, 2022**

### What’s New

Mule 3.8 and 3.9 EOL messages are shown in API Manager for:

- APIs running on Mule 3.8, which has already reached end of life and whose extended support ended
  on **November 16, 2021**.

- APIs running on Mule 3.9, whose standard support ended on **March 20, 2021**.

Improved user experience over Flex 1.2.0 new features:

- Adding port sharing validation.

## 2.4.5

**September 28, 2022**

### What’s New

Flex Gateway information shown in API Manager has been enhanced as follows:

- Flex Gateway data representation on API Manager charts is improved.

- Message logs can now be viewed and downloaded in order from latest to oldest.

- The message log streaming information now specifies log level, such as **Info**, **Warn**, and
  **Error**.

## 2.4.4

**August 25, 2022**

### What’s New

The SLA Tiers, Contracts, and Client applications sections are improved for a better experience:

- For SLA Tiers, the delete and deprecate actions are now found in the context menu at the end of
  each tier.

- For Contracts:

  - The Pending tier change status is now named Approved (pending tier change). The current tier and
    requested tier can now be edited using the pencil icon without opening the application detail
    information.

  - The text in the column now changes from N/A to - when there is no current tier or requested
    tier.

  - The Refresh functionality is now added.

- For Client applications:

  - The Pending contract column now shows the amount of pending contracts for each application.

  - Owners are now shown by email and not by name.

  - The Pending tag is now added to the drop-down options for APIs, API versions, API instances,
    group, group versions, and group instances to search for pending contracts easily.

### Fixed Issues

- For Contracts:

  - The Status filter now considers all contracts for the api and not just the contracts shown in
    the current view.

  - The Requested SLA tier can now be changed when a contract is in the Approve (pending tier
    change) status.

## 2.4.3

**July 29, 2022**

### What’s New

- API Manager now notifies you when policy implementations are incompatible with your current Flex
  Gateway version.

- Applying a Message Logging policy to your API instance in API Manager allows you to view basic
  message logs for APIs managed by Flex Gateway within API Manager.

## 2.4.2

**July 28, 2022**

### What’s New

- You can now sort by the **Error Rate** and **Total Requests** columns in the API Manager **API
  Administration** page.

## 2.4.1

**June 22, 2022**

### New Features

The alerts section has been improved for a better experience:

- Clicking an alert will now show its details. To edit an alert, you can use the context menu icon.

- Added an icon in the **State** column explaining each state in detail when you hover on it.

## 2.4.0

**May 2, 2022**

MuleSoft announces the release of API Manager 2.4.0.

### New Features and Enhancements

The following new features and enhancements are introduced in API Manager 2.4.0:

- You can now manage Flex Gateway APIs.

- The new API Wizard introduces a streamlined way to create APIs.

- Policy and automated policy management have been improved.

- The release introduces a new way to create custom policies for Mule 4 and Flex Gateway.

- The behavior of some policies has changed. For example, The IP Allowlist and IP Blocklist policies
  no longer accept a comma-separated list. The policies now accept data formatted as an array.

For details, see [Anypoint API Manager](https://docs.mulesoft.com/api-manager/latest/latest-overview-concept).

## 2.3.0

**August 12, 2021**

MuleSoft announces the release of API Manager 2.3.0.

### New Features and Enhancements

The following new features and enhancements are introduced in API Manager 2.3.0:

- The API list view has been redesigned to enable quick glances at important information, without
  having to click into specific API instances.

- In the redesigned API list, you can now view total requests and error rates for an API (for the
  previous 24 hours).

For details, see [What Anypoint API Manager Is](https://docs.mulesoft.com/api-manager/latest/latest-overview-concept).

## 2.2.16

**June 4, 2021**

This release introduces the following enhancement:

- Enhanced the UI to have the Mule 4 version selected by default for APIs.

- Fixed bugs and implemented security improvements.

## 2.2.15

**October 20, 2020**

### Fixed Issues

API proxies were responding with an unexpected HTTP status code when an API policy rejected an
incoming HTTP Request.

### Known Issues

None.

## 2.2.14

**May 30, 2020**

This release introduces platform-wide support for API Groups across API Manager, Exchange, and API
Community Manager, enabling you to package multiple API instances into a single cohesive unit for
your API consumers.

API consumers can access the published API Groups from Anypoint Exchange and API Community Manager.
For more information about this feature, see
[API Groups](https://docs.mulesoft.com/api-manager/latest/api-groups-landing-page).

### Fixed Issues

None.

### Known Issues

None.

## 2.2.13

**April 02, 2020**

This release introduces support for multiple identity providers for client management. You can now
assign different client identity providers to business groups, environments, and APIs.

Configuring multiple client providers enables you to enforce security and regulations in your
business organization.

For more information about this feature, see
[Configuring Multiple Client Providers](https://docs.mulesoft.com/api-manager/latest/configure-multiple-credential-providers).

## 2.2.12

**October 5, 2019**

This release provides this new feature:

- Support for WSDL and RAML payload validations for Mule 3 and Mule 4 proxy applications.  
  See [API Proxy Validations](https://docs.mulesoft.com/api-manager/latest/api-proxy-landing-page) for more information.

## 2.2.11

**May 4, 2019**

This release provides this new feature:

- Improved UI modal for changing Mule 3 custom policy version.

## 2.2.10

**April 6, 2019**

This release provides this new feature:

- Support for Mule 4 API proxy versions in API configuration

### Fixed in This Release

- Incorrect user information received in request api access email

- Federated users unable to create APIs

## 2.2.9

**Jan 26, 2019**

This release provides this new feature:

- Automated policy for Mule 4 APIs

- Adding RAML support for "Create new API"

- While creating an API instance, API version and asset version are prepopulated

- When deploying Mule 4 to CloudHub it is possible to choose specific runtime version

- Notification for a managed API if API spec changes or newer version available in Exchange

## 2.2.8

**December 21, 2018**

This release provides this new feature:

- JWT policy for Mule 4 APIs

## 2.2.7

**November 17, 2018**

This release provides this new feature:

- Domain support for Mule 4

### Fixed in This Release

- Bug when users download a HTTPS proxy without TLS context.

- Changed policy display order, sorting version in descending order.

## 2.2.6

**November 3, 2018**

This release provides this new feature:

- API Manager 2.x users will get access to Secrets Manager.

- Configure, secure & deploy HTTPs proxies using certificates (keystore/truststore) stored in
  Secrets Manager. This feature will be available for Mule 4 APIs deployed to CloudHub & Hybrid
  deployment targets.

## 2.2.5

**August 30, 2018**

This release provides this new feature:

- User-defined ports for CloudHub deployments

- Added "Manage Runtime Fabric" proxy link

- Auto populate implementation URI from Exchange

- Support for Analytics chart to every granular permission

### Fixed in This Release

- Bug when users couldn’t add tags

- Bug when users with custom roles weren’t receiving email notifications for API access

## 2.2.4

**June 30, 2018**

This release provides this new feature:

- Caching Policy for Mule 4 APIs

## 2.2.3

**June 2, 2018**

This release provides this new feature:

- Changes in platform APIs for unclassified environments to facilitate CI/CD pipelines.

### Fixed in This Release

- Bug when cannot save a change in API configuration. (AP-4030)

- Bug when Mule 4 Runtime in a business group is unable to retrieve contracts. (AP-4081)

## 2.2.2

**May 17, 2018**

This release provides these features:

- Fine-grained access control for the November release of API Manager 2.0.

- Logging and Header injection and removal policy for 3.8.5+ runtimes.

- On the API Settings page "Client Applications" has been renamed to "Contracts".

- Bug fixes.

### Fixed in This Release

- Bug when displaying client ID enforcement details. (AP-3976)

- Exporting a Mule 4 API containing a policy resulted in a "TypeError: Cannot read property"
  message. (AP-3941)

- If a valid URL with OAuth was copied from API Manager, and the user then logged out, subsequent
  attempts to access the URL failed with an NPE. (AP-3907)

- Redeploy button incorrectly disabled after a deploy. (AP-3955)

- When a user only has Asset Admin permission in Anypoint Exchange, the action of making the API
  Instance public or private fails. (AP-3860)

- Allow updating these fields, which were set to read-only after the November upgrade: api.name,
  api.groupId (also updates the apiversion.groupId), api.assetId (also updates the
  apiversion.assetId), and apiversion.name. (AP-4020)

## 2.2.1

**April 23,2018**

This release includes these improvements and bug fixes.

- Support for 3.9 proxies.

- Fixes an issue when approval email was not sent after requesting access for published APIs with
  manual approval.

- Fixes an issue with autocomplete on import from Exchange.

- Improved error message when deleting Client Applications with OKTA as the IM provider.

- When autodiscovery looks for API ID that does not exist, Platform returns 403 instead of 404.

## 2.2.0

**January 27, 2018**

This release supports deployment for Mule 4.1.0 proxies on the November release.

## 2.0.0

**November 18, 2017**

This release of API Manager includes new and enhanced features for accounts that have upgraded to
the November release. If your account hasn’t been upgraded yet, please contact your Customer Success
representative.

### Key Changes and Enhancements

- A tight integration of Anypoint Platform components extends the
  [use of environments](https://docs.mulesoft.com/api-manager/latest/environments-concept) to API management.

- API permissions are now environment-based.

- You can now [create multiple instances](https://docs.mulesoft.com/api-manager/latest/api-instance-landing-page) of an
  API.

- APIs in Exchange can be
  [managed from API Manager](https://docs.mulesoft.com/api-manager/latest/create-instance-task-mule).

- There are two new APIs for managing APIs:

  - API Manager API v1.0 to manage API.

  - API Manager proxy API v1.0 to manage deployment of API proxies through API Manager.

- Support for Mule 4 Early Access. Mule 4-related changes to API Manager are:

  - Classloader isolation exists between the application, the runtime and the connectors, and
    policies.

  - This release of Mule 4
    [changes the packaging, size, and scope](https://docs.mulesoft.com/api-manager/latest/policy-scope-size-concept) of
    a policy.

  - All policies are non-blocking.

  - All policies except CORS, which is executed first, can be ordered.

- [Custom policy development](https://docs.mulesoft.com/mule-gateway/policies-custom-getting-started) has changed.

- Header propagation no longer occurs by default and needs to be configured.

- Resource level policy support, which was restricted to RAML-based APIs, is extended to any HTTP
  API.

### Changes Related to Using Mule 4 Early Access

- API Manager
  [does not support auto-generation and deployment of proxies](https://docs.mulesoft.com/api-manager/latest/latest-overview-concept).

- The Throttling policy is not supported in this Mule release.

- Mule 4 replaces the security manager policies with two HTTP Basic Authentication policies:

  - A combination of HTTP Basic Authentication and Simple Security Manager

  - A combination of HTTP Basic Authentication and LDAP Security Manager

    The policy protects an API by expecting and validating a user name and password.

- You can configure the Rate Limiting policy if the quota is shared among the cluster nodes or not.
  By default, the quota is shared among the cluster nodes.

## See Also

- [Troubleshooting](https://docs.mulesoft.com/api-manager/latest/troubleshooting-landing-page)

- [Known Issues](https://help.salesforce.com/s/issues)