Batch mode

Batch mode provides asynchronous transcription for large or complex jobs that require processing multiple files or lengthy recordings.

Capabilities

• Parallel file processing
• Asynchronous operation
• Large-scale recording support
• Multi-speaker and multi-channel audio support

Each audio file generates its own transcript that saves to a corresponding output location.

How it works

Batch mode processing runs asynchronously and enables you to transcribe multiple files in a single API call.

This mode is ideal for workflows that involve multi-channel audio or large file collections.

Input

The API supports three input modes.

Output

The API supports three output layouts.

Audio formats

WAV, MP3, M4A, and MP4

Transcription options

These options control transcription language, segmentation mode, and channel separation.

Batch jobs

Create a batch job

To create a new batch transcription job, use this endpoint:

POST /aiservices/scribe/jobs

You can optionally include a reference_id for tracking.

To receive webhook notifications when a job finishes, include a notifications object with a webhook_url and a secret for payload verification.

Example request (cURL)

This cURL example submits a batch transcription job from S3 and defines the output location and settings. The response returns a job ID and status so you can track processing.

curl -X POST https://api.zoom.us/v2/aiservices/scribe/jobs \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "mode": "PREFIX",
      "source": "S3",
      "uri": "s3://acme-bucket/audio/2025/11/",
      "filters": {
        "include_globs": ["**/*.wav", "**/*.mp3"],
        "exclude_globs": ["**/tmp/**"]
      },
      "auth": {
        "aws": {
          "access_key_id": "AKIA...",
          "secret_access_key": "wJalrX...",
          "session_token": "FwoGZXIvYXdzE..."
        }
      }
    },
    "output": {
      "destination": "S3",
      "uri": "s3://acme-bucket/transcripts/2025/11/",
      "layout": "PREFIX",
      "auth": {
        "aws": {
          "access_key_id": "AKIA...",
          "secret_access_key": "wJalrX...",
          "session_token": "FwoGZXIvYXdzE..."
        }
      }
    },
    "config": {
      "language": "en-US",
      "word_time_offsets": true,
      "channel_separation": true
    },
    "notifications": {
      "webhook_url": "https://example.com/hooks/scribe",
      "secret": "hmac-secret"
    },
    "reference_id": "import-2025-11"
  }'

Response (201)

{
    "job_id": "job_abc123",
    "state": "QUEUED",
    "submitted_at": "2026-01-05T18:34:12Z"
}

Batch job endpoints

Three additional endpoints are available to manage batch jobs.

Webhook verification

When you provide a secret in the notifications object, the API signs each webhook request so you can verify that Zoom AI Services sent it.

Each webhook request includes two headers.

To verify the signature:

1. Compute the HMAC-SHA256 of the string v0:{timestamp}:{raw_body} using your secret key
2. Compare it with the value in x-zm-signatureusing a timing-safe comparison to prevent timing attacks.
3. Reject the request if the signatures do not match or if the timestamp is stale.

const message = `v0:${timestamp}:${rawBody}`;
const expected = `sha256=${crypto.createHmac("sha256", secret).update(message).digest("hex")}`;
const isValid = crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected),
);

Per-file processing status

Use the following endpoint to retrieve per-file processing status for a batch job.