Google announced on its Developers blog that API Gateway now supports real-time streaming in Public Preview.confirmed This update allows developers to route long-lived, bi-directional streams and AI workloads directly through the gateway. The service maintains consistent authentication, rate limiting, and observability for these connections without requiring changes to existing API specifications.
Evidence: confirmed
Streaming comes to API Gateway: real-time and AI-ready APIs, without changing your specaifleet-google-dev
The claim
Google stated that streaming endpoints can now sit behind the same gateway as other APIs, governed by the same policies. Previously, developers had to choose between using the gateway and losing streaming capabilities, or routing streaming traffic around the gateway and losing security controls. The company claims this eliminates the need for a split estate of governed and ungoverned traffic.company claim
The response
The announcement highlights that no new extensions, annotations, or separate specifications are needed for streaming operations. The same document describing existing APIs also describes streaming APIs. During Public Preview, users opt in via a single flag when creating the gateway. At General Availability, streaming is planned to be the default behavior without any opt-in requirement.
The practical upshot
API Gateway now supports Server-Sent Events, chunked transfer encoding, WebSockets, and gRPC streaming. Streams can remain open for up to one hour. The update also introduces deterministic default hostnames, removing the previously generated hash from default URLs. This change simplifies infrastructure-as-code management by allowing developers to know gateway URLs before creation.
Claims versus evidence
Google claims that streaming support strengthens its connection to the Gemini platform by enabling model routing for Gemini, Claude, and OpenAI gpt-oss models. The evidence provided is the technical capability to stream responses from these models as they are generated. The source acknowledges that clients should implement reconnection logic for long-lived connections. No independent testing results are cited.
Why it matters
- Product teams can keep AI inference endpoints under the same security policies as standard APIs, reducing governance complexity.
- Developers do not need to rewrite API specifications or learn new resource types to enable streaming, lowering adoption friction.
- Deterministic hostnames improve infrastructure-as-code workflows by removing unpredictable URL generation during environment provisioning.
- Support for SSE and WebSockets allows real-time features like live dashboards to use the same gateway infrastructure as transactional APIs.
Topics: Google Cloud, API Gateway, Streaming, AI Infrastructure, Server-Sent Events
Updated
Ask the article
Local keyword search of this article; no generated answers.Which of these is confirmed?
Check the answer
Google announced on its Developers blog that API Gateway now supports real-time streaming in Public Preview.
The matched primary source and announcement wording support the confirmed label.
Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
Does enabling streaming require changing my existing OpenAPI specification?
No, Google states that streaming support works with existing API specifications without requiring new extensions or annotations.
What streaming protocols does API Gateway support?
It supports Server-Sent Events, WebSockets, gRPC streaming, and chunked transfer encoding including newline-delimited JSON.
How long can a streaming connection stay open?
Streams can stay open for up to one hour, though clients should implement reconnection logic for session survival.
Connected stories
Reading receipt
- API Gateway now supports Server-Sent Events, WebSockets, gRPC streaming, and chunked transfer encoding.
- The feature is available in Public Preview and requires no changes to existing API specifications or OpenAPI documents.
- Deterministic default hostnames are now available, simplifying infrastructure-as-code management and environment provisioning.