Global Traffic Management (GTM) is designed to enable Internet users to access their websites or any other IP application quickly and reliably. GTM applies an Internet-centric approach to global load balancing to provide high-site availability and responsiveness to online user requests. Unlike traditional hardware-based solutions that reside within the data center, Akamai’s Global Traffic Management service is a fault-tolerant solution that makes intelligent routing decisions based on real-time data center performance health and global Internet conditions to route online user requests to the most appropriate data center using an optimized Internet route for that user at that moment. Additional capabilities include:

Battle tested. Routes and manages traffic for some of the world’s largest distributed user audiences.

Massive scale. Provides the scale to absorb the largest DDoS attacks targeting the DNS infrastructure.

Roles and permissions. Provides configuration access controls to limit who can view and edit configurations.

The latest update for API Gateway includes the following enhancements:

Activating a registered API no longer changes the last modified date for that registered API.

The Reset to API settings button in API Definitions is clearly separated from other elements in the UI.

GraphQL settings are no longer visible for registered APIs with the GraphQL feature turned off.

The UI for OAuth scopes clearly shows all APIs and resources each scope is associated with.

The tool for comparing API versions in API Definitions includes GraphQL and OAuth scopes settings.

When importing a Swagger file without an API name, the server URL is no longer used as a replacement for the API name in API Definitions. Instead, API Gateway returns a 400 HTTP error response indicating that an API name should be specified in the Swagger file.

The email alerts received after activating an API are more user-friendly.

A bug that caused failed activations of APIs for some customers has been fixed.

2018-11-15

The latest update for API Gateway includes the following features and enhancements:

New features:

You may now access API Dashboard in Control Center to view various charts with data about your APIs. The data appears with only a five-minute delay which lets you discover and troubleshoot issues proactively. (BETA ONLY)

Enhancements:

In the API Endpoint Definition API, you may now import and re-import API definition files by making an application/json request to ease file upload.

You may now add descriptions to OAuth scopes that you create in API Definitions.

You may now define and validate any JWT public and private claims. You are no longer limited to using only reserved claims in a token.

The dialog box that appears when switching from RESTful to GraphQL caching now includes clearer messaging to ease workflow.

2018-09-18

The latest update for API Gateway includes the following features and bug fixes.
Please note that much of the work in this release are deliverables for API Gateway 1.1 beta program.

New features:

You can now specify in API Definitions whether your API uses GraphQL to deliver structured content to clients. If so, you can configure specific caching settings for your GraphQL API. (BETA)

You can customize selected error messages that your APIs return to clients. This includes the error message response body, HTTP status code, and headers. (BETA)

Fixed bugs:

Key collection names must be at least 1 character in length.

Responses for “not-null” and “type-mismatch” errors returned in the API Endpoint Definition and API Keys and Traffic Management APIs are more descriptive and informative.

The latest update for API Gateway includes the following features and bug fixes:

New features:

You can customize cache keys by specifying whether to use a query string in an incoming request to differentiate objects in a cache.

Fixed bugs:

API registration form with numerous resources renders more quickly.

The Activate button in the Activate API window is always available.

Quota reports show the correct graph for non-existing data.

The manual quota reset is reflected correctly in quota reports.

When importing an API definition file, all resources can be saved after you modify one of the imported resources.

Reimporting Swagger files no longer produces internal server errors.

Reimporting YAML files no longer produces internal server errors.

The daily quota reset is displayed properly in quota reports.

More accurate error messages are returned for quota headers-related errors.

The error message for incorrect origin hostname is more transparent.

API error messages are consistent in capitalization.

The new text in the key import modal now clearly states that the import operation appends keys to a collection.

The CSV format example in the key import modal now includes the description field.

2018-07-05

The latest update to API Gateway introduces a new functionality that lets you hide inactive API configurations from the registered APIs list as well as individual API configuration versions from the version history panel. This contributes to a more transparent and clutter-free interface.

2018-06-11

The latest updates for API Gateway include:

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 OpenAPI 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.