Use this method to submit text to be synthesized. The synthesize output will use features from the provided audio file to mimic the speech within the audio.
Audio and text files are submitted via a HTTP multipart form POST. Each file is included as a multipart file attachment within the POST. The service supports several different formats for the audio file. The text must be a plain utf-8 encoded text file.
Request body
The multipart request body containing both text and audio file fields.
E.g.
Content-Type: multipart/form-data; boundary=------------------------2e3fcd51d85aad0a
------------------------2e3fcd51d85aad0a
Content-Disposition: form-data; name="audio"; filename="abc.wav"
Content-Type: audio/wav
audio data
------------------------2e3fcd51d85aad0a
Content-Disposition: form-data; name="text"; filename="abc.txt"
Content-Type: text/plain
untimed text data
------------------------2e3fcd51d85aad0a--
User request completion callback
When submitting a request, an optional HTTP callback can be specified which will be invoked when the request completes or fails. The callback is an HTTP POST to the exact URL provided. Only one attempt is made to reach the URL provided. The contents of the HTTP request match the response from the Query text to speech request status and retrieve results method.
Headers
x-requestid- Contains the request_id received when the request was submittedx-status- One of the following indicating the status of the request:
| Status | Description |
|---|---|
| “Completed” | The request has finished processing and the user callback, if provided has been called. |
| “Failed” | An error occurred processing the request. |
x-error- If the request failed, this would contain an error message.x-userdata- This will contain the user data supplied with the original request.
Body
If the status is “Completed” the body of the request contains the default SRT result from the alignment. If the status is “Failed” the body of the request contains the same error message provided in the “x-error” header.