• You are no longer redirected to the first key collection after refreshing or making changes on the Key and Quota Management page.
• A blank base path is now treated as equivalent to a base path of /* during API configuration activation.
• The Quota usage by time report is now available under Reporting in Control Center.
• The Akamai API for quota reports is now a part of the Key and Quota API.
• Each contract has a default API keys limit (1000 keys) that you can change by contacting your account representative.
• You can upload API definition files in a Swagger 3.0 format.
• You can overwrite hostnames and base paths during the import operation.
• The Quota used last updated field in Key and Quota Management includes a time zone.
• The UI in Key and Quota Management clearly displays which keys are selected across all collections.

• CreatedBy and UpdatedBy fields returned in OpenAPI contain user-friendly data.
• Activation and deactivation operations in OpenAPI return data in the response body.
• Key and Quota Management contains information about the latest update of keys’ remaining quota.
• You are no longer redirected to the first collection after generating keys.
• The tag limit per API key is 10.
• The default clock skew value for JWT claims validation is five seconds.
• The import interface now clearly reflects reimporting for existing API configurations.
• You can control whether resources inherit API privacy, JWT validation, and caching settings from the API level.

The LA version of API Gateway is available and includes the following updates:

• Importing an API definition file via URL doesn’t prompt for a root file field anymore.
• The Activate button on the API registration page is grayed out if another version activation is pending.
• The labels in the Compare Versions window reflect the field names in the UI.
• You can hide the left-hand side column with key collections in Key and Quota Management to improve the visibility of keys data in the table.
• Users with read-only permissions cannot create, activate, or clone endpoints.
• You can see the remaining quota for each individual key in Key and Quota Management.
• The API definition re-import mechanism detects if the hostnames being imported differ from the existing hostnames. If yes, you get a warning that original hostnames will not be replaced.
• During API activation, a version with conflicting hostnames is not deactivated when not all hostnames are in conflict.

• Quota enforcement is now available.
• Akamai APIs for quota, key management, and Gateway features are now available.
• You can now import Swagger 2.x files in YAML format in addition to JSON format.
• Activation emails are now available for API configurations when you deploy them to the network.
• Historical reports for API activity are now available.