New features and enhancements

If you are assigned the Administrator role, you can export the following asset types from an organization and import them into another organization:

This enhancement gives you the flexibility to transfer assets across organizations without needing to re-create them.

For more information, see Asset Management.

If you are assigned an Administrator or Deployer role, you can export and rename the following asset types:

You can make an asset with the same name exportable in the same location. When you export duplicate asset, API Center appends a timestamp after the asset name.

To rename the duplicate asset, use the Rename option from the Actions menu.

For more information, see Asset Management.

You can move folders and assets on the Explore page.

However, you can't move an asset to a folder that contains an asset of the same type and name. You can't move a design API from one location to another.

For more information, see Asset Management.

When you define operation parameters for a REST API and you enter path parameters or query parameters, the parameters are automatically detected and added to the parameters table.

When you define an endpoint, any placeholder enclosed in curly braces (for example, /users/{userId}) are automatically added to the Path parameters section of the Parameters table. This is a unidirectional process, which means that the data flows only from the endpoint definition to the table. You can't manually add or delete these auto-populated parameters in the table. You can't edit the parameter key, but you can edit the data type and description of the key parameters.

Query parameters are separated from the URL by a question mark (?). Query parameters synchronize bidirectionally. Changes made in the endpoint URL are instantly reflected in the Query parameters section of the Parameters table, and any parameters added or edited in the table automatically updates the URL. Use the table provides to add, delete, and edit parameter attributes.

For more information, see REST API Assets.

To cater to API auditing requirements, API Center now provides a new View OAuth 2.0 Client dialog box to display the OAuth 2.0 client details.

This view includes the OAuth 2.0 Client's name, description, ID and token details, associated resources, such as managed APIs and API groups, and important timestamps.

For more information, see API Policies.

To ensure full HTTP standards compliance and improve compatibility with a wider range of API clients, all GET APIs now automatically support the HEAD HTTP method.

When a HEAD request is sent to a GET endpoint, the API returns only the metadata of the response headers without the message body, as specified by the HTTP standard.

The Swagger definition doesn't contain explicit details for the HEAD method. The HEAD method automatically inherits all rate limit and authorization policies from the corresponding GET method.