Merge pull request #2448 from eric-urban/eur/audio-patch-1

audio completions preview

Author: prmerger-automator[bot]

articles/ai-services/openai/includes/audio-completions-intro.md

@@ -29,6 +29,8 @@ The `gpt-4o-audio-preview` model is available for global deployments in [East US
 
 Currently the following voices are supported for audio out: Alloy, Echo, and Shimmer.
 
+The maximum audio file size is 20 MB.
+
 > [!NOTE]
 > The [Realtime API](../realtime-audio-quickstart.md) uses the same underlying GPT-4o audio model as the completions API, but is optimized for low-latency, real-time audio interactions.
 

articles/ai-services/openai/quotas-limits.md

@@ -52,6 +52,7 @@ The following sections provide you with a quick guide to the default quotas and
 | GPT-4 `vision-preview` & GPT-4 `turbo-2024-04-09` default max tokens | 16 <br><br> Increase the `max_tokens` parameter value to avoid truncated responses. GPT-4o max tokens defaults to 4096. |
 | Max number of custom headers in API requests<sup>1</sup> | 10 |
 | Message character limit | 1048576 |
+| Message size for audio files | 20 MB |
 
 <sup>1</sup> Our current APIs allow up to 10 custom headers, which are passed through the pipeline, and returned. Some customers now exceed this header count resulting in HTTP 431 errors. There's no solution for this error, other than to reduce header volume. **In future API versions we will no longer pass through custom headers**. We recommend customers not depend on custom headers in future system architectures.