Google API Gateway adds streaming preview with a new-gateway requirement

Google [announced API Gateway streaming in Public Preview on October 22](https://developers.googleblog.com/streaming‑comes‑to‑api‑gateway‑real‑time‑and‑ai‑ready‑apis‑without‑changing‑your‑spec/), adding a way to pass incremental model responses and other long‑lived traffic through its API management layer. The preview supports Server‑Sent Events, progressively delivered HTTP responses including newline‑delimited JSON, WebSockets, and server‑side and bidirectional gRPC streaming. Google says streaming responses pass through as the backend produces them rather than being buffered until completion. For an AI application, the practical reader question is whether the gateway can carry an ongoing response while the backend continues its work. This announcement addresses that transport choice; it does not provide a measured latency or reliability result. The API description itself does not need streaming‑specific annotations, extensions or a separate specification, according to Google. The company also says API key enforcement, JWT validation, service‑account authentication to backends, logging, monitoring and request routing continue to apply. These are descriptions of the service, rather than an OpenTools test of a deployed configuration.

The [preview opt‑in belongs to gateway creation](https://developers.googleblog.com/streaming‑comes‑to‑api‑gateway‑real‑time‑and‑ai‑ready‑apis‑without‑changing‑your‑spec/): the `gcloud api‑gateway gateways create` command adds `--enable‑streaming` while selecting an API and API configuration. Streaming is not a new property that teams add to their API configuration. Existing gateways cannot be converted in place. A team trying the preview therefore needs to create a new streaming‑enabled gateway, even when it can reuse its existing API description. That distinction matters for rollout planning: an unchanged API contract does not mean the existing gateway resource gains streaming automatically. Google says it plans to remove the opt‑in at general availability. The October 22 announcement describes Public Preview; that future default is not a current GA promise with a published delivery date.

At the [initial Public Preview launch](https://developers.googleblog.com/streaming‑comes‑to‑api‑gateway‑real‑time‑and‑ai‑ready‑apis‑without‑changing‑your‑spec/), streaming enablement through the Cloud console and Terraform are unavailable. The post also excludes custom domains through Serverless network endpoint groups and an external Application Load Balancer from that initial preview. Those are specific streaming‑preview limitations, not a statement that the wider console, Terraform or load‑balancing products are unavailable. The announcement also introduces a deterministic default hostname: `GATEWAY_ID‑PROJECT_NUMBER.REGION.gateway.dev`. Google says this lets teams derive the address from the gateway ID, project number and region before creating the resource. It can help prepare client configuration or allowlists, while leaving the separate preview restrictions on streaming deployment tools in place.

Google says [streams can stay open for up to one hour](https://developers.googleblog.com/streaming‑comes‑to‑api‑gateway‑real‑time‑and‑ai‑ready‑apis‑without‑changing‑your‑spec/) and advises clients to implement reconnection logic. Applications need to handle the end of a connection as part of the session design, rather than treating a streaming connection as permanent. The monitoring definition also needs attention. For a streaming connection, API Gateway request latency measures the life of the stream, not time to first byte. A longer value can therefore describe a connection that remained open to deliver data. Teams assessing initial response time need to distinguish that question from the stream‑duration metric; this announcement supplies no independent speed comparison. *Photo: [Lambtron](https://commons.wikimedia.org/wiki/User:Lambtron) / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Google_data_center.jpg), [CC BY‑SA 4.0](https://creativecommons.org/licenses/by‑sa/4.0/). Google data center in The Dalles, Oregon, June 23, 2020. Archive company context; not evidence that API Gateway streaming is hosted or routed at this site. Display crop and downscale; image adaptations retain the same licence.*