Introduction

This API enables its users to interact with Audio Data Cloud (ADC) and perform actions on the audio content. Submit new audio content, update already processed content, fetch outputs...

The system is asynchronous for all the processes with API being the exception. So to have an audio file transcribed you send a request to the API, and wait for the webhook to inform you about the specific resource being available. The webhook will be fired for each atomic part of the process (transcript ready, brand safety ready etc).

Resource structure:

1. Tenant - represents an account. The resource has some metadata attached to it, but has no practical usage.
2. Audio - highest level of hierarchy. This resource has all of the processed data attached to it.
3. Transcription, Brand Safety, Summary, Keywords, Chapters... - These are processed data of the audio file.