Skip to main content

Overview

The Batch Processor is an API that performs post-processing jobs on your call media. It accepts a recording ID from a Daily meeting or a URL to a video/audio file (e.g. mp4, mp3) and can produce a transcript of the audio, or a summary of the transcript generated from the audio.

Types of jobs

There are few predefined post-processing jobs that the batch processor can perform from the audio of a media file:
  1. Generate a transcript
  2. Generate a summary

Post-call transcripts

The batch processor can generate transcripts from the audio of a media file. The transcription is powered by Deepgram.

Example transcripts

Transcripts are formatted as txt, srt, vtt, and json. Text:
SRT:
VTT:
JSON:

Post-call summaries

The batch processor can generate summaries from the audio of a media file.

Example summary

The summary is written as a text file. An example file looks like this (this is fake data):

Feature configuration

These configuration options are optional domain properties. They affect every batch processing job on a Daily domain. By default, batch processor outputs are stored with Daily’s HIPAA-compliant storage.
Property NameTypeDescriptionDefault
batch_processor_bucketobjectDefines a custom S3 bucket where the batch processor will write its output to.null (output stored at Daily)
This is the same style configuration as setting up your own custom S3 storage for recordings. Please note: if recordings_bucket property was set on either the domain or room configuration when a recording was made, then when passing in the resulting recording id to a batch processor POST request, the domain configuration for recordings_bucket must match the recording configuration.