Merge pull request #7775 from alexeyo26/alexeyo/rt-wss-no-api-version

Elaborating on Realtime WSS URLs

Author: prmerger-automator[bot]

articles/ai-foundry/openai/how-to/realtime-audio-websockets.md

@@ -33,8 +33,6 @@ The GPT real-time models are available for global deployments in [East US 2 and
 - `gpt-realtime` (`2025-08-28`)
 - `gpt-realtime-mini` (`2025-10-06`)
 
-You should use API version `2025-04-01-preview` in the URL for the Realtime API. 
-
 For more information about supported models, see the [models and versions documentation](../concepts/models.md#audio-models).
 
 ## Prerequisites
@@ -56,25 +54,25 @@ You can construct a full request URI by concatenating:
 - The secure WebSocket (`wss://`) protocol.
 - Your Azure OpenAI resource endpoint hostname, for example, `my-aoai-resource.openai.azure.com`
 - The `openai/realtime` API path.
-- An `api-version` query string parameter for a supported API version such as `2024-12-17`
 - A `deployment` query string parameter with the name of your `gpt-4o-realtime-preview`, `gpt-4o-mini-realtime-preview`, or `gpt-realtime` model deployment.
+- - **(Preview version only)** An `api-version` query string parameter for a supported API version such as `2025-04-01-preview`
 
 The following example is a well-constructed `/realtime` request URI:
 
-#### [preview version](#tab/preview)
+#### [GA version](#tab/ga)
 
 ```http
-wss://my-eastus2-openai-resource.openai.azure.com/openai/realtime?api-version=2025-04-01-preview&deployment=gpt-4o-mini-realtime-preview-deployment-name
+wss://my-eastus2-openai-resource.openai.azure.com/openai/v1/realtime?model=gpt-realtime-deployment-name
 ```
-#### [GA version](#tab/ga)
+
+#### [Preview version](#tab/preview)
 
 ```http
-wss://my-eastus2-openai-resource.openai.azure.com/openai/v1/realtime?model=gpt-realtime-deployment-name
+wss://my-eastus2-openai-resource.openai.azure.com/openai/realtime?api-version=2025-04-01-preview&deployment=gpt-4o-mini-realtime-preview-deployment-name
 ```
 
 ---
 
-
 To authenticate:
 - **Microsoft Entra** (recommended): Use token-based authentication with the `/realtime` API for an Azure OpenAI resource with managed identity enabled. Apply a retrieved authentication token using a `Bearer` token with the `Authorization` header.
 - **API key**: An `api-key` can be provided in one of two ways: