OpenAI API / OpenAI API

OpenAI Realtime API invalid_beta Error After OpenAI-Beta Header Deprecation

Fix OpenAI Realtime API invalid_beta error after OpenAI-Beta realtime header deprecation Includes evidence for OpenAI API troubleshooting demand.

Source-backed Last updated May 12, 2026 1 source Needs local verification

Category: OpenAI API
Error signature: Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 12, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for OpenAI API, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API is a OpenAI API failure pattern reported for developers trying to fix openai realtime api invalid_beta error after openai-beta realtime header deprecation. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

LiteLLM PR #27690 (May 2026) documents the OpenAI API deprecation. realtime_translation_testing CircleCI job fails on every PR with: {"error": {"code": "invalid_beta", "message": "Unknown beta requested: 'realtime'."}} followed by TimeoutError: Timed out waiting for 'session.created'. OpenAI deprecated the OpenAI-Beta: realtime=v1 header.

Common causes

OpenAI deprecated the OpenAI-Beta: realtime=v1 header on the live Realtime API. Applications still sending this header receive {'error': {'code': 'invalid_beta', 'message': "Unknown beta requested: 'realtime'."}} followed by a TimeoutError waiting for 'session.created'. This breaks CI/CD pipelines and production integrations that haven't been updated.
LiteLLM PR #27690 (May 2026) documents the OpenAI API deprecation. realtime_translation_testing CircleCI job fails on every PR with: {"error": {"code": "invalid_beta", "message": "Unknown beta requested: 'realtime'."}} followed by TimeoutError: Timed out waiting for 'session.created'. OpenAI deprecated the OpenAI-Beta: realtime=v1 header.

Quick fixes

Confirm the exact error signature matches Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API.
Check the OpenAI API account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API exactly before applying the quick fix.
Compare the failing environment with OpenAI API versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API mean in OpenAI API?

Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API indicates the workflow described by "OpenAI Realtime API invalid_beta Error After OpenAI-Beta Header Deprecation" failed in a OpenAI API context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API?

Check whether this cause matches your environment: OpenAI deprecated the OpenAI-Beta: realtime=v1 header on the live Realtime API. Applications still sending this header receive {'error': {'code': 'invalid_beta', 'message': "Unknown beta requested: 'realtime'."}} followed by a TimeoutError waiting for 'session.created'. This breaks CI/CD pipelines and production integrations that haven't been updated.

Is the Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API guidance source-backed?

The "OpenAI Realtime API invalid_beta Error After OpenAI-Beta Header Deprecation" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API?

For "OpenAI Realtime API invalid_beta Error After OpenAI-Beta Header Deprecation", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Unknown beta requested: 'realtime' — invalid_beta error on OpenAI Realtime API?

For "OpenAI Realtime API invalid_beta Error After OpenAI-Beta Header Deprecation", collect the failing OpenAI API command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.