Migration guide from Gladia V1 API to the V2 API
Upload your file
/upload
endpoint with multipart/form-data
content-type since Gladia /v2/pre-recorded
endpoint only accept audio URLs now.More information about this step in the API Referenceaudio_url
.Transcribe
/audio/text/audio-transcription
now we’ll use /v2/pre-recorded
/v2/pre-recorded
does not accept any audio
file, Content-Type
is not
multipart/form-data
anymore, but application/json
.id
and a result_url
.id
is your transcription ID that you will use to get your transcription result once it’s done. You don’t have to keep any HTTP connection open on your side.result_url
is returned for convenience. This is a pre-built url with your transcription id in it that you can use to get your result in the next step.
Get the transcription result
Polling
id
and a pre-built result_url
for convenience.
To get the result with this method, you’ll just have to GET continuously on the given result_url
until the status
of your transcription is done
.You can get more information on the different transcriptions status by checking directly the API Reference.Webhook
POST
request will be made to the endpoint you configured. The request body is a JSON object containing the transcription id
that you can use to retrieve your result with our API.Callback URL
callback
feature to receive the result to a specified endpoint:callback_config.url
using the HTTP method you provided in callback_config.method
.
Allowed methods are POST
and PUT
with the default being POST
.The request body is a JSON object containing the transcription id
and an event
property that tells you if it’s a success or an error.V1 | V2 |
---|---|
toggle_diarization | diarization |
language_behaviour | detect_language , enable_code_switching , language |
output_format | subtitles + subtitles_config |
webhook_url | callback_url |