This page contains release notes for features and updates to API Gateway. You can see the latest product updates for all of Google Cloud on the [Google Cloud](https://docs.cloud.google.com/release-notes) page, browse and filter all release notes in the [Google Cloud console](https://console.cloud.google.com/release-notes), or programmatically access release notes in [BigQuery](https://console.cloud.google.com/bigquery?p=bigquery-public-data&d=google_cloud_release_notes&t=release_notes&page=table). To get the latest product updates delivered to you, add the URL of this page to your [feed reader](https://wikipedia.org/wiki/Comparison_of_feed_aggregators), or add the [feed URL](https://docs.cloud.google.com/feeds/apigateway-release-notes.xml) directly. ## November 04, 2026 v1 Announcement **Negative backend deadlines are no longer deprecated** The deprecation of negative backend `deadline` values announced on October 23, 2026 is withdrawn. In an OpenAPI 2.0 `x-google-backend` extension or a gRPC `BackendRule`, a negative deadline continues to use the default deadline, the same as `0`, and won't be rejected. OpenAPI 3.x backends still reject a negative deadline. For more information, see [OpenAPI 2.0 extensions](https://docs.cloud.google.com/api-gateway/docs/oasv2-extensions#deadline) and [OpenAPI 3.x extensions](https://docs.cloud.google.com/api-gateway/docs/oasv3-extensions#backends_object). ## November 03, 2026 preview \& v1 Feature **Call Google Cloud APIs from streaming gateways** Streaming gateways can now call Google Cloud APIs such as `aiplatform.googleapis.com`. A gateway with an `effectiveStreamingMode` of `EFFECTIVE_STREAMING_MODE_ENABLED` authenticates to backends whose host ends in `.googleapis.com` or `.vertexai.goog` with an access token for the gateway's service account. Other backends still receive an ID token. An existing streaming gateway switches when API Gateway next rolls out a gateway update, or immediately when you update it to a new API config. For more information, see [Securing backend services](https://docs.cloud.google.com/api-gateway/docs/securing-backend-services#other-gcp-apis). ## October 23, 2026 v1 Deprecated **Negative backend deadlines are deprecated** A negative backend `deadline` in an OpenAPI 2.0 `x-google-backend` extension or a gRPC `BackendRule` uses the default deadline, the same as `0`. Negative values there are deprecated and will be rejected in a future release; until then, creating an API config with one returns a warning in the operation metadata. OpenAPI 3.x backends already reject a negative deadline. To use the default, omit the field or set it to `0`. For more information, see [OpenAPI 2.0 extensions](https://docs.cloud.google.com/api-gateway/docs/oasv2-extensions#deadline) and [OpenAPI 3.x extensions](https://docs.cloud.google.com/api-gateway/docs/oasv3-extensions#backends_object). ## September 30, 2026 preview \& v1 Feature **Authenticate MCP tool discovery with an API key** API key authentication is now supported for the Model Context Protocol (MCP) `tools/list` method. You can name an API key security scheme in `tools-list.security`, in addition to a JWT security scheme. For more information, see [Configure Model Context Protocol](https://docs.cloud.google.com/api-gateway/docs/mcp-configure). ## September 29, 2026 preview \& v1 Feature **Configure streaming for LLM responses and other traffic** You can now create API Gateway gateways that stream requests and responses instead of buffering them. This Public Preview feature supports incremental response delivery over HTTP/2 or HTTP/1.1 chunked transfer encoding, Server-Sent Events (SSE), WebSockets, and gRPC bidirectional streaming. A common use is streaming token-by-token responses from a large language model (LLM). To enable streaming, create a gateway with the `--enable-streaming` flag. The streaming mode is fixed when you create the gateway and can't be changed later. For more information, see [Configure streaming for LLM responses and other traffic](https://docs.cloud.google.com/api-gateway/docs/streaming-configure). ## September 11, 2026 preview \& v1 Feature **Enable Model Context Protocol (MCP)** You can now configure API Gateway to act as a remote Model Context Protocol (MCP) server. This Public Preview feature allows you to expose your existing REST APIs to AI agents as tools, without requiring changes to your backend services. You can enable MCP by annotating your OpenAPI 3.x specification using custom Google extensions. For more information, see [Model Context Protocol overview](https://docs.cloud.google.com/api-gateway/docs/mcp-overview) and [Configure Model Context Protocol](https://docs.cloud.google.com/api-gateway/docs/mcp-configure). ## September 03, 2026 preview \& v1 Change **New model routing gateways might use a gateway.dev default hostname** If you create a gateway that uses model routing on or after September 3, 2026, it might receive a `gateway.dev` default hostname instead of a `run.app` one, in the form `https://GATEWAY_ID-PROJECT_NUMBER.REGION.gateway.dev` --- for example, `https://my-gateway-123456789012.us-central1.gateway.dev`. This is a second `gateway.dev` format; other gateways keep the existing one. To get a gateway's URL, read its `defaultHostname` property. For more information, see [Deploy an API to a gateway](https://docs.cloud.google.com/api-gateway/docs/deploying-api). ## August 03, 2026 preview \& v1 Feature **Route LLM requests with model routing** You can now use model routing in API Gateway as a managed traffic management layer to accept OpenAI-compatible prompt requests, transcode them in-flight, and route them to specific foundation models in Gemini Enterprise Agent Platform Model Garden (including Gemini, Anthropic Claude, and OpenAI GPT models). Key benefits and capabilities include: - **Centralized traffic management**: Consolidate AI traffic routing and lifecycle management at the network edge without hosting standalone client-side proxies. - **In-flight transcoding**: Standardize client applications on an OpenAI-compatible REST interface while dynamically dispatching requests to diverse underlying Agent Platform Model Garden endpoints. - **OpenAPI 3.x configuration** : Define model routing tables, explicit routing rules, and default model fallbacks using the new `x-google-api-management.ai.models.routing` and `x-google-model-router` OpenAPI 3.x extensions. For more information, see [Overview of model routing](https://docs.cloud.google.com/api-gateway/docs/model-routing-overview) and [Configure model routing](https://docs.cloud.google.com/api-gateway/docs/model-routing-configure). ## June 18, 2026 v1 Change **Update to the API Gateway runtime architecture** The API Gateway runtime architecture is being updated to improve its integration with Google Cloud Platform and its services. This update does not affect existing API Gateway features. However, be aware of the following differences: - Status code changes for **gRPC** API Gateways | Error | New status code | Previous status code | |---|---|---| | Quota exceeded | `ResourceExhausted` | `Unavailable` | | Invalid API key | `InvalidArgument` | `InternalError` |
- For 4xx client-side quota failures, API Gateway will now reject requests (fail closed). This applies to both **gRPC** and **OpenAPI** API Gateways. If you experience any other differences in behavior due to this update, contact [Google Cloud Customer Care](https://cloud.google.com/support-hub). **Note**: Rollouts of this release to production instances might take up to 4 weeks to complete across all Google Cloud zones. Your instances might not be updated until the rollout is complete. ## April 27, 2026 v1 Change **New validations on paths in API configurations** API Gateway now enforces stricter syntax validations on templated paths when you create new API configurations and gateways. See [path templating syntax rules](https://docs.cloud.google.com/api-gateway/docs/path-templating#syntax_rules) and [limits](https://docs.cloud.google.com/api-gateway/docs/path-templating#limits) for more information. ## February 02, 2026 v1 Change **Connect API Gateway to Apigee API hub instances that use VPC Service Controls** API Gateway can now be [connected to Apigee API hub](https://docs.cloud.google.com/api-gateway/docs/api-hub-connect) instances that use [VPC Service Controls](https://docs.cloud.google.com/apigee/docs/api-platform/security/vpc-sc). ## January 12, 2026 v1 Feature **Centralize API Gateway API management using Apigee API hub** Connect API Gateway to Apigee API hub to enable seamless publishing of API metadata from your API Gateway project to API hub. This integration provides a centralized, unified view of your APIs across different gateways, simplifying API discovery, governance, and management. Key benefits include: - **Centralized API discovery**: All your API Gateway APIs are discoverable in API hub alongside APIs from other sources - **Enhanced visibility**: Gain insights into your API landscape with consolidated metadata - **Streamlined management**: Simplify API governance and lifecycle management across your diverse API ecosystem For more detail, see [Centralize API management using API hub](https://docs.cloud.google.com/api-gateway/docs/api-hub-overview). **Note**: Rollouts of this release to production instances might take up to 5 business days to complete across all Google Cloud zones. Your instances might not have the feature available until the rollout is complete. ## November 12, 2025 v1 Feature **API Gateway now supports OpenAPI version 3.0.** With this release, API Gateway now supports OpenAPI version 3.0, including all patch versions (3.0.x). Key Benefits: - Simplified Deployment: Directly upload and deploy OpenAPI version 3.0.x specifications without prior conversion to 2.0. - Enhanced Compatibility: Seamlessly integrate your OpenAPI version 3.0.x definitions with API Gateway. For more detail, see [OpenAPI overview](https://docs.cloud.google.com/api-gateway/docs/openapi-overview). v1 Announcement On November 12, 2025, we released a new version of API Gateway. ## July 23, 2025 v1 Deprecated **Deprecation of Transport Layer Security (TLS) v1.0 and v1.1 protocols** API Gateway now enforces TLS v1.2+. You can opt out of enforcing TLS v1.2+ for your API Gateway's new security settings by reaching out to [Google Cloud Support](https://docs.cloud.google.com/support) to continue using your current protocol. Connections using TLS 1.1 and earlier will return a `400 Bad Request - The request was malformed` error after a successful TLS handshake, indicating that the connection is established, but the request itself is denied. External SSL-checking sites may verify a successful TLS handshake and incorrectly imply that TLS versions 1.1 and earlier are supported. v1 Announcement On July 23, 2025, we released an updated version of API Gateway. ## June 09, 2025 v1 Feature With this release, the limit on the number of API gateways that can be created per region is increased to **50**. For more information, see [Quotas and limits](https://docs.cloud.google.com/api-gateway/docs/quotas) v1 Announcement On June 9, 2025, we released an updated version of API Gateway. ## April 02, 2025 v1 Announcement On April 2, 2025, we released an updated version of API Gateway. v1 Feature With this release, API Gateway meets the regulatory and compliance requirements for support of data residency for data at rest. For more information, see [Google Cloud Platform Services with Data residency](https://cloud.google.com/terms/data-residency?e=48754805). ## March 26, 2025 v1 Announcement On March 26, 2025, we released an updated version of API Gateway. v1 Feature With this release, customer data in API Gateway is now CMEK-compliant at rest. No configuration is required. For more information, see [CMEK compliance in API Gateway](https://docs.cloud.google.com/api-gateway/docs/cmek). To learn more about CMEK, see [Customer-managed encryption keys (CMEK)](https://docs.cloud.google.com/kms/docs/cmek). ## March 25, 2025 v1 Announcement On March 25, 2025, we released an updated version of API Gateway. v1 Feature API Gateway now supports [Workforce Identity Federation](https://docs.cloud.google.com/iam/docs/workforce-identity-federation). Workforce Identity Federation lets you use an external identity provider (IdP) to authenticate and authorize a workforce --- a group of users, such as employees, partners, and contractors --- using [Identity and Access Management (IAM)](https://docs.cloud.google.com/iam/docs) to access API Gateway services. See [Identity federation: products and limitations](https://docs.cloud.google.com/iam/docs/federated-identity-supported-services) for more information. ## July 01, 2024 v1 Announcement **As of July 1, 2024, API gateways located in `asia-east1` are decommissioned and will no longer serve traffic.** Between **October 2021** and **October 2022** , customers with gateways located in `asia-east1` were notified of the planned decommissioning and advised to delete or relocate any gateways in this region. A final reminder was sent in May, 2024. As of July 1, 2024, any remaining gateways located in `asia-east1` are fully decommissioned. ## March 16, 2023 v1 Fixed Fixed issue where API Gateway used the IP address of the Google Cloud Load Balancer (GCLB) (specifically the address of the forwarding rule) to validate IP-restricted API keys in requests proxied by a GCLB. API gateway now correctly validates IP-restricted API keys using the IP address of the client calling the GCLB. ## January 05, 2023 v1 Fixed | Bug ID | Description | |---|---| | 266369520 | **Fixed issue where gRPC requests to a gateway resulted in `400` responses following an ESPV2 upgrade.** | v1 Change When calling a gateway using gRPC with transcoding, every field provided in a request message must contain a valid value. For every field included in the request message you must either specify a valid integer value or remove the field entirely. ## August 09, 2021 v1 Announcement Released a Preview version of HTTP(S) Load balancing for API Gateway. The integration of [Google Cloud HTTP(S) Load Balancing](https://docs.cloud.google.com/load-balancing/docs/https) support for API Gateway enables your serverless backends to take advantage of all the features provided by Cloud Load Balancing. By combining API Gateway and HTTP(S) Load Balancing using a [serverless Network Endpoint Group (serverless NEG)](https://docs.cloud.google.com/load-balancing/docs/negs), you can: - Host gateways with custom branded domains - Configure TLS for gateways using certificates issued by a preferred certificate authority - Create a common entry point for a gateway routing to multiple backends - Deploy gateways in multiple geographic regions for high availability without managing URLs for each region To provide feedback or to log issues with this release, see [Getting support](https://docs.cloud.google.com/api-gateway/docs/getting-support). ## January 21, 2021 v1 Feature An updated [REST API reference](https://docs.cloud.google.com/api-gateway/docs/reference/rest) for the `v1` version is available. v1 Feature API Gateway support for the `us-east1` region is now available. v1 Feature API Gateway is added to the gcloud command group. Users should upgrade to the latest `gcloud` release to access the API Gateway command group. v1 Feature gRPC support is available for Cloud Run backend services. For more information, see [Getting started with API Gateway and Cloud Run for gRPC](https://docs.cloud.google.com/api-gateway/docs/get-started-cloud-run-grpc). v1 Announcement Released a GA version of API Gateway. To provide feedback or to log issues with this release, see [Getting support](https://docs.cloud.google.com/api-gateway/docs/getting-support). ## September 08, 2020 v1beta Issue Projects with gateways created between July 14, 2020 and August 6, 2020 may encounter an issue when new gateways are created with the beta API. The `*gateway.dev` hostname of the new gateway may return a `404` error response. A resolution to this issue is in progress. In the meantime, we recommend creating or using a new Google Cloud project when using the beta API. v1beta Feature The API Gateway API is now publicly visible. Allowlisting is no longer required to view or enable the API in your Google Cloud project. Deprecated fields are no longer present in alpha versions of the API and the [API Gateway UI](https://console.cloud.google.com/api-gateway) utilizes the beta API. v1beta Announcement Released a beta version of API Gateway. To provide feedback or to log issues with this release, see [Getting support](https://docs.cloud.google.com/api-gateway/docs/getting-support). v1beta Issue When creating an API config, and in particular the *first* config for a new service, the operation may take several minutes to complete as the config is propagated to downstream systems. Creation of a complex API config could take up to ten minutes to complete successfully. v1beta Issue Gateways created during alpha with `*.run.app` hostnames (created prior to July 14, 2020) will be turned down shortly after the beta release. We recommend creating new gateways using the `v1beta` API. Gateways created with the beta API will have `*.gateway.dev` hostnames. v1beta Issue API configs created prior to June 2, 2020 can no longer be deployed to gateways. These configs will be deleted through an internal process. v1beta Issue API Gateway built-in IAM roles are not initially visible. As a result, management permissions are not displayed on the permissions panel within the [API Gateway UI](https://console.cloud.google.com/api-gateway). However, permissions to manage API Gateway resources can be granted as expected via Project Owner, Editor, and Viewer roles. A resolution to this issue is in progress. v1beta Feature An updated [REST API reference](https://docs.cloud.google.com/api-gateway/docs/reference/rest) for the `v1beta` version is available. v1beta Issue API Gateway does not support custom IAM roles. A resolution to this issue is in progress. v1beta Feature API Gateway is added to the `gcloud beta` command group. Alpha users and trusted testers should upgrade to the latest `gcloud` release to access the API Gateway beta command group. v1beta Feature Newly created gateways have an updated default hostname pattern: `https://GATEWAY_ID-HASH.REGION_CODE.gateway.dev` where **GATEWAY_ID** is the name of the gateway, **HASH** is the unique hash code generated when you deployed the gateway, and **REGION_CODE** is the code for the Google Cloud region where the gateway is deployed. For more information, see [Deploying an API to a gateway](https://docs.cloud.google.com/api-gateway/docs/deploying-api). ## July 01, 2020 v1alpha2 Feature Updated the [REST API reference](https://docs.cloud.google.com/api-gateway/docs/reference/rest) to the latest Alpha version. v1alpha2 Issue When creating a gateway, permissions can take more than a minute to propagate through the system. Therefore, you might see a "missing tokens" error when making a request to an API. If you see this error, wait several minutes, then retry the request. v1alpha2 Announcement Released an updated version of the Alpha version of API Gateway. To provide feedback or to log issues with this release, see [Getting support](https://docs.cloud.google.com/api-gateway/docs/getting-support). v1alpha2 Feature Newly created gateways now have an updated default hostname pattern: `https://GATEWAY_ID-HASH.REGION_CODE.gateway.dev` where **GATEWAY_ID** is the name of the gateway, **HASH** is the unique hash code generated when you deployed the gateway, and **REGION_CODE** is the code for the Google Cloud region where the gateway is deployed. For more information, see [Deploying an API to a gateway](https://docs.cloud.google.com/api-gateway/docs/deploying-api). v1alpha2 Feature OpenAPI specifications for API configs no longer require the `host` property. You can either omit the `host` property entirely or set it to the DNS name of the deployed API. API providers often set it to the DNS name when sharing the OpenAPI Spec with their API consumers. However, the value of the `host` property is not enforced by API Gateway. Do not set the `host` property to **null** or an empty value, as this will result in an error. For more information, see [OpenAPI overview](https://docs.cloud.google.com/api-gateway/docs/openapi-overview). v1alpha2 Issue When creating an API config, and in particular the *first* config for a new service, the operation may take several minutes to complete as the config is propagated to downstream systems. Creation of a complex API config could take up to ten minutes to complete successfully. ## April 01, 2020 v1alpha2 Fixed Previously, when the `gcloud` command failed while creating an API config, the API config was still created, requiring you to manually delete it. The `gcloud` command no longer requires you to delete the API config when the create command fails. v1alpha2 Feature The [`gcloud` command-line tool](http://cloud.google.com/sdk/gcloud) now supports new command options, including: - Create, list, update, and delete APIs. That means you no longer have to use [Cloud Endpoints](https://docs.cloud.google.com/endpoints/docs) commands to work with an API. See [Creating an API](https://docs.cloud.google.com/api-gateway/docs/creating-api) for more. - Update an API config to modify its labels or display name. See [Updating an API config](https://docs.cloud.google.com/api-gateway/docs/creating-api-config#updating-an-api-config) for more. v1alpha2 Feature You can now use the Google Cloud Console UI, a web-based, graphical user interface, to develop your APIs. See the [Quickstart: Use the UI to deploy an API on API Gateway](https://docs.cloud.google.com/api-gateway/docs/quickstart-console) for more. v1alpha2 Issue When creating a gateway, permissions can take more than a minute to propagate through the system. Therefore, you might see a "missing tokens" error when making a request to an API. If you see this error, wait several minutes, then retry the request. v1alpha2 Announcement Alpha update release of API Gateway Released an updated version of the Alpha version of API Gateway. To provide feedback or to log issues with this release, see [Getting support](https://docs.cloud.google.com/api-gateway/docs/getting-support). v1alpha2 Feature Updated the [REST API reference](https://docs.cloud.google.com/api-gateway/docs/reference/rest) to the latest Alpha version. v1alpha2 Issue Authentication is only supported for Cloud Run and Cloud Functions, not for App Engine. ## March 01, 2020 v1alpha1 Issue When creating a gateway, permissions can take more than a minute to propagate through the system. Therefore, you might see a "missing tokens" error when making a request to an API. If you see this error, wait several minutes, then retry the request. v1alpha1 Issue Authentication is only supported for Cloud Run and Cloud Functions, not for App Engine. v1alpha1 Announcement Released the Alpha version of API Gateway. To provide feedback or to log issues with this release, see [Getting support](https://docs.cloud.google.com/api-gateway/docs/getting-support).