Key New Features

• Added the ability to publish a Proxy to the Developer Portal.
• Added conditional mapping rules between a Proxy endpoint and an upstream API.
• Added support for Open API Specification (OAS) 3.0 in creating and publishing an API. Generated specifications still use OAS 2.0.
• Added the ability to enable the Try It Out feature for all APIs in the Developer Portal.
• Added the ability to specify custom subscription key parameters.
• Replaced Token authorization with Bearer authorization for new API requests in the Developer Portal.

New Features

• Proxy Mapping Rules You can now create Proxy Mapping Rules to map your Proxy endpoints to the right target depending on the conditions. Learn more about Proxy Mapping Rules.
• Proxy Publication You can also publish Proxies in the API Manager. In the Developer Portal, they appear like other APIs. Learn more about publishing a Proxy.
• Dynamic Search Dynamic Search is now available in the API Manager.
• CORS Org-wide Setting for “Try It Out” Org Administrators can now enable the “Try It Out” feature for all APIs in the Developer Portal using a default CORS Restriction Policy. However, if a CORS Restriction Policy exists at the API level or API version level, it has precedence over the default Org-wide policy. Learn more about setting up the Developer Portal.
• Auto-Approve Subscriptions When you publish an API or Proxy, you can now choose to auto-approve requests for subscriptions to the API. Learn more about publishing an API version or Proxy.
• Custom Subscription Key Parameters When you publish an API or Proxy, you can specify the header or the query parameter that the API consumer must set to the subscription secret key. Learn more about publishing an API version or Proxy.
• Fast Secret Copy API consumers can also copy the application's secret key by clicking the key icon (:SL-devport-key:) on the application's card, instead of having to edit the application entry to copy the secret key.

Enhancements

• Open API Specification (OAS) 3.0 The API Manager now accepts OAS 3.0 specifications for APIs; however, API consumers can download only OAS 2.0 specifications.
• Bearer Authorization Header When calling an API with an approved subscription, you must set the Authorization header as Authorization: Bearer <client secret>, instead of using Token.
• Featured APIs In the Grid View of the Developer Portal, featured APIs are now easier to find with the existence of the Featured pill at the top of the API card. Featured APIs appear at the top of the API list. The API's tags are also displayed as pills at the bottom of the card.
  
  
  
  
• New Documentation Article Using Long-running Triggered Tasks with an Enterprise Scheduler describes how to use a script to prevent timeout or lost connection errors when executing long-running tasks from an enterprise scheduler. The script starts Pipeline execution and polls continuously for completion status. This keeps the connection alive and prevents the scheduler from reporting an error.

Known Issues

• API Dashboard
  • The API Dashboard does not collect metrics for APIs that do not generate a response entity.
  • When the API Management feature is enabled for the Org, the API Dashboard does not automatically start collecting data. You must restart the Snaplex nodes and allow the Dashboard to start.
• CORS Setting Delay In the Portal Manager > Settings tab, changes to CORS Setting > Enable Try Me might not take effect for up to two hours due to caching. This occurs only in JCC nodes with Snaplex Version 4.28 and older.
• No notification about modified Key Settings If an API is republished with modified Key Settings, existing subscribers are not notified of the change.