![]() ![]() Some request frameworks provide an incompatible default value. The Speech service provides results in JSON. If provided, it must be application/json. Required if you're sending chunked audio data. The Speech service acknowledges the initial request and awaits additional data. If you're using chunked transfer, send Expect: 100-continue. Use this header only if you're chunking audio data. Specifies that chunked audio data is being sent, rather than a single file. ![]() Accepted values are audio/wav codecs=audio/pcm samplerate=16000 and audio/ogg codecs=opus. To learn how to build this header, see Pronunciation assessment parameters.ĭescribes the format and codec of the provided audio data. This parameter is a Base64-encoded JSON that contains multiple detailed parameters. These scores assess the pronunciation quality of speech input, with indicators like accuracy, fluency, and completeness. Specifies the parameters for showing pronunciation scores in recognition results. For more information, see Authentication.Įither this header or Ocp-Apim-Subscription-Key is required. Your resource key for the Speech service.Įither this header or Authorization is required.Īn authorization token preceded by the word Bearer. This table lists required and optional headers for speech to text requests: Header The Speech SDK supports the WAV format with PCM codec as well as other formats. The preceding formats are supported through the REST API for short audio and WebSocket in the Speech service. It must be in one of the formats in this table: Format Audio formatsĪudio is sent in the body of the HTTP POST request. Replace with the identifier that matches the region of your Speech resource.įor Azure Government and Azure China endpoints, see this article about sovereign clouds. The endpoint for the REST API for short audio has this format: For more information, see Authentication. You should always use the Speech to text REST API for batch transcription and Custom Speech.īefore you use the Speech to text REST API for short audio, understand that you need to complete a token exchange as part of authentication to access the service. Batch transcription and Custom Speech are not supported via REST API for short audio.Speech translation is not supported via REST API for short audio.The REST API for short audio returns only final results.The input audio formats are more limited compared to the Speech SDK. Requests that use the REST API for short audio and transmit audio directly can contain no more than 60 seconds of audio.Use it only in cases where you can't use the Speech SDK.īefore you use the Speech to text REST API for short audio, consider the following limitations: Use cases for the Speech to text REST API for short audio are limited.
0 Comments
Leave a Reply. |