Using the Recommended Callback Flow
If you specify a callback, results are sent to the specified endpoint as soon as transcription completes. Your callback server must be able to receive multipart POSTs that contain the requestid of the result and the results themselves. For example, you could use a command like the following to simulate the data that would be sent by V‑Cloud to your callback server.
curl -F "file=@test.zip;type=application/zip" \ -F requestid=700e7496-4fce-4963-aa7b-b3b26600f813 \ https://vcloud.vocitec.com/trancribe/result
This command provides the two fields of the multipart POST that your callback server needs to be able to handle. Ensure that your callback server correctly returns success (HTTP code 200) when these two fields are received.
Results are deleted from V‑Cloud once the callback succeeds.
Tip
Using the /transcribe/result
method in conjunction with a callback is not recommended, because you will only be able to retrieve results if the callback has failed.
See Receiving Transcription Results for more information about the data that V‑Cloud sends to a callback server.
The following example demonstrates asking the service to send transcription results to a callback server, specifying none but the minimum number of required options.
curl -F callback=https://www.example.com:5555
\ -F "file=@sample7.wav
;type=audio/x-wav" \ -F token=123e4567e89b12d3a456426655440000 \ http://vcloud.vocitec.com/transcribe
This sample command instructs the V‑Cloud service to send a JSON transcript of the audio file sample7.wav
to a callback server available on the Internet at https://www.example.com:5555
.