Answer: A gateway should forward server-sent events (SSE) incrementally rather than buffering the entire answer, preserving event types and payloads including the successful terminal `response.completed` event, and forwarding error and failure events so the client can distinguish a failed response from a stalled connection. Status: Confirmed Entry: tool/codex/integrations/gateway-streaming-requirements Revision: 1 Digest: sha256:e9361bfeb17a27ed (changes whenever the content changes) Timeline: Created: 2026-11-13T03:49:56Z Last changed: 2026-11-13T03:49:56Z Last verified: 2026-11-20T13:38:00Z Next check: 2026-11-21T13:38:00Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of streaming method | server-sent events (SSE) | [1] | 2026-11-20 terminal event | response.completed | [1] | 2026-11-20 error handling | Forward error and failure events | [1] | 2026-11-20 verification | load balancers and reverse proxies | [1] | 2026-11-20 Sources: [1] OpenAI. "Gateway compatibility requirements". https://learn.chatgpt.com/docs/enterprise/gateway-compatibility.md Role: primary. Accessed: 2026-11-20T13:38:00Z Quote: "Forward server-sent events (SSE) incrementally rather than buffering the entire" (Supports: streaming method) Quote: "including the successful terminal `response.completed` event" (Supports: terminal event) Quote: "Forward error and failure events so the client can" (Supports: error handling) Quote: "Verify the full stream through load balancers and reverse proxies as well as the" (Supports: verification) Snapshot SHA-256: 12e67546a9838a10adcc791affb295a4fe662d2636438759e9212d6011b678ad (captured 2026-11-13T03:49:56Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:49:56Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:38:00Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:38:00Z Last attempt: 2026-11-20T13:38:00Z Notes and limitations: Extracted automatically from a single official source (section "Streaming"). Related: https://latestn.com/tool/codex/integrations/github-action-prerequisites What are the prerequisites for using the Codex GitHub Action in a workflow? https://latestn.com/tool/codex/integrations/gitlab-ci-requirements What are the requirements to run Codex Security in GitLab CI/CD? https://latestn.com/tool/codex/integrations/gitlab-code-review-prerequisites What do I need before setting up Codex code review for GitLab? https://latestn.com/tool/codex/integrations/experimental-api-opt-in How do I opt in to experimental APIs in the Codex app-server? https://latestn.com/tool/codex/integrations/export-servicenow How do I export Codex Security findings for ServiceNow? https://latestn.com/tool/codex/integrations/gateway-required-endpoints What endpoints must a gateway support for Codex to work with the Responses API? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:49:56Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/integrations/gateway-streaming-requirements/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/integrations/gateway-streaming-requirements POST: https://latestn.com/dispute/tool/codex/integrations/gateway-streaming-requirements with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/integrations/gateway-streaming-requirements?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How should a gateway handle streaming for Codex? Revision 1, last verified 2026-11-20T13:38:00Z. https://latestn.com/tool/codex/integrations/gateway-streaming-requirements (accessed 2026-11-21T10:00:26Z). @misc{LatestN_tool_codex_integrations_gateway_streaming_requirements_r1, title = {How should a gateway handle streaming for Codex?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/integrations/gateway-streaming-requirements}}, note = {Revision 1; digest sha256:e9361bfeb17a27ed; last verified 2026-11-20T13:38:00Z; accessed 2026-11-21T10:00:26Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/integrations/gateway-streaming-requirements