What's New > July 2025 > Changed behaviors
  

Changed behaviors

The July 2025 release of API Center includes the following changed behaviors.

OAuth 2.0 security authentication for API groups

When you create or edit an API group or managed API group, you can enable OAuth 2.0 authentication at the API group level. You can then invoke the APIs in the managed API group with OAuth 2.0 or third-party authorization access tokens.
When you enable API-level authentication for an API group, all the operation-level authentications are overridden. However, this behavior doesn't apply to custom API operations.
Previously, you couldn't enable OAuth 2.0 authentication at the API group level. You could enable OAuth 2.0 authentication only at the operation level.
For more information, see Manage APIs.

Naming convention changes

To include OAuth 2.0 authentication at the API group level, a field has been renamed as described in the following table:
Page or Tab Name
Old Field Name
New Field Name
API Groups page > API Groups tab > <Create or edit an API group> > Policies tab
JWT Access Token
Security
API Groups page > Managed API Groups tab > <Create or edit a managed API group> > Policies tab
JWT Access Token
Security
For more information, see Manage APIs.

Inclusion of query parameters in managed and custom managed API endpoint URLs

When your REST API operation endpoint includes query parameters, API Center now automatically displays the complete endpoint URL with those parameters for both managed APIs and custom managed APIs. This enhancement ensures consistency between your endpoint definitions and query parameter configurations.
In a managed API, you can use the following formats for query parameters:
In a custom managed API, you can use the following format for a query parameter:
Query key and value (?param=value)
Previously, query parameters were not displayed in the managed API endpoint URL, even when they were defined during the creation of the managed API.
For more information, see Manage APIs.

Distinct tabs for APIs and API groups while configuring OAuth 2.0 clients and defining user permissions for third-party authentication

When you configure an OAuth 2.0 client or third-party user permission, you'll now see the managed APIs and managed API groups categorized under the following tabs:
With this enhancement, the APIs are now organized into distinct tabs, making it easier to locate and interact with the specific resources you need.
Previously, you could view both API types in a single, combined view requiring you to scroll to reach the next section. This made navigation inefficient and time-consuming.
For more information, see Manage APIs.