POST /assets
request to our API:url
returned (in the response) as the destination for uploading your asset:render
object (you can read more about that here, under 'Constructing the render object')render
object, you can now use the asset id
as a source (instead of a public url
). The elements being used must match that type of asset (in this case, video).id
instead of the url
. The request looks like this:clean: true
field into the body of the request, and your file will be cleaned from all background noise, as soon as it's uploaded:transcribe: true
field into the body of the request when creating an asset, and any speech that is detected will be transcribed into text, as soon as it's uploaded. The text will be stored in the transcription
field of the asset object once finished: