Official documentation
Speech to text REST API for short audio
Microsoft Learn (Azure AI Speech), n.d.
Read the originalRead on October 16, 2026
- What it is
- Microsoft's reference for the Azure AI Speech short-audio REST endpoint. It lists the optional profanity parameter and its three values, and the default.
- How much weight it carries
- Official vendor documentation for Azure AI Speech, read on the accessed date. Describes the API, not the behavior of any consumer app. The page is undated.
Facts taken from this source
- Azure AI Speech's display text applies inverse text normalization, which converts spoken text to shorter forms, such as 200 for two hundred.
“Inverse text normalization is conversion of spoken text to shorter forms” (Response properties)
- Azure AI Speech's profanity setting defaults to masked, which replaces profanity with asterisks.
“which replaces profanity with asterisks” (profanity parameter)
- Azure AI Speech's profanity setting has a raw option, which includes profanity in the recognition result, so the words are returned as recognized.
“which includes profanity in the result. The default setting is masked” (Optional parameters for the detailed response, profanity)
- Azure AI Speech offers a removed option that drops all profanity from the recognition result.
“which removes all profanity from the result” (profanity parameter)
- Azure's REST speech to text API needs a language parameter in the URL, or the request can fail with a 4xx error.
“You must append the language parameter to the URL to avoid receiving a 4xx HTTP error.” (Query parameters)
- Azure's REST API for short audio does not support batch transcription or custom speech.
“Batch transcription and custom speech aren't supported via REST API for short audio.” (Limitations)
- Azure's REST API for short audio accepts no more than 60 seconds of audio in a request when the audio is sent directly.
“Requests that use the REST API for short audio and transmit audio directly can contain no more than 60 seconds of audio” (Limitations)
- Azure's REST API for short audio returns only final results, without partial text while the speaker is still talking.
“The REST API for short audio returns only final results. It doesn't provide partial results.” (Limitations)
- Azure's REST API for short audio requires the audio to be in one of the formats its page lists, which is a narrower set than the Speech SDK accepts.
“It must be in one of the formats in this table” (Audio formats)
- Azure's REST speech to text API accepts your Speech resource key in the Ocp-Apim-Subscription-Key header.
“When you're using the Ocp-Apim-Subscription-Key header, only your resource key must be provided” (Authentication)