prepare media
Several reads of up to 20 library items, started in one call: transcript, search_index (a video’s moments, for search_footage), speech (where speech sits, read by remove_silence and duck_music), speakers, beats, levels (loudness). A read already stored answers ready and starts nothing; every other is queued as its own job, or answers skipped, refused or held (the computer reading it holds it back) with the reason, and the rest still start. job_ids goes to one get_jobs call; each read is stored on its item as its job succeeds, and transcribe_media, speakers, detect_beats and search_footage then return it free. estimate is the cloud minutes started and what is left. A repeat call starts nothing twice. Cloud processing.
Authorizations
An API key (es_live_…) from Settings, under API keys, or an OAuth access token.
Headers
Retry a paid dispatch safely: the same key returns the job already dispatched instead of charging again.
The workspace this one call acts in, when it is not the default: for a key or a connected agent, one of the workspaces the user allowed it.
Body
1 to 20 items.
1 - 20 elementsAn item ref, item id, or the job id that made it.
The reads to start. speakers reads speech too. One that does not apply to an item's type is skipped.
1transcript, search_index, speech, speakers, beats, levels Optional: one sentence shown to the user beside this action.
600
