The April 2025 release of API Center includes the following new features and enhancements.
Real-time monitoring of APIs
You can gain real-time visibility into API health, including response times, latency, errors, and traffic. Additionally, you can access detailed analytics on API usage patterns, user behavior, and performance trends over time. You can use this data to optimize API operations, identify bottlenecks, and ensure compliance effectively.
Multibyte character support
You can use multibyte characters, including Japanese characters for the following API Center assets:
•Operation name
•API name
•Published API name
•Managed API name
•Policy name
•OAuth 2.0
•Context
•API group name
•Managed API group name
•Custom API name
Import Application Integration processes to API Center
You can import all the published REST API processes of Application Integration to API Center. You can import the processes on the Service Name corresponds to the API Name, and the Source Name corresponds to the process Name in Application Integration.
This import capability enables a seamless transition of published Application Integration processes to API Center, streamlining the design, publication, and creation of managed of APIs.
Date and Date Time data type
When you define the request and response body of an API operation, you can select the Date and Date Time data types. You can also create an array type of Date and Date Time data type.
Enhanced OAuth 2.0 support
You can now assign multiple managed APIs and managed API groups to an OAuth 2.0 Client, improving API authorization and streamlining OAuth 2.0 Client credential management. With this enhancement, disabling or deleting an OAuth 2.0 Client will immediately invalidate its authorization token, preventing API access and enhancing security.
This improvement enhances API security and management by eliminating the need for multiple OAuth 2.0 Clients. You can create a single OAuth 2.0 Client to grant access to specific API sets, simplifying authorization control.
Edit operation policies in API groups
You can edit policies that are in created and inactive states of a Managed API group. Editing such policies enables you to reuse API groups with the same operations while applying different policies and context names.
You can also attach different policies to different operations when creating active managed API groups and hence ensures that you can reuse Published APIs directly from the API Console.
API-level rate limit policy at operation level for API groups
When designing an API, if you associate an API-level rate limit policy but do not assign policies to individual API operations, the API-level rate limit policy is automatically applied to the operations when you add the API to an API group. The active managed API groups will also enforce the applied rate limit.