MeetStream Guide: Per-Participant Audio Streams

This guide explains how to capture individual audio recordings per participant in a meeting. Instead of a single mixed audio track, you receive a separate WebM audio file for each speaker.

Supported platforms: Google Meet, Zoom.

1) What you need

1. A MeetStream API key (refer to Dashboard Setup).
2. A meeting link (Google Meet or Zoom).
3. Set audio_separate_streams: true in your Create Bot request.

2) Create a bot with per-participant audio

Use the Create Bot endpoint: https://docs.meetstream.ai/api-reference/ap-is/bot-endpoints/create-bot

Minimal example

$
curl -X POST "https://api.meetstream.ai/api/v1/bots/create_bot" \
>
  -H "Authorization: Token <YOUR_API_KEY>" \
>
  -H "Content-Type: application/json" \
>
  -d '{
>
    "meeting_link": "<YOUR_MEETING_LINK>",
>
    "bot_name": "RecorderBot",
>
    "audio_separate_streams": true
>
  }'

Full example with recording config

1
{
2
  "meeting_link": "https://meet.google.com/abc-defg-hij",
3
  "bot_name": "RecorderBot",
4
  "audio_separate_streams": true,
5
  "recording_config": {
6
    "transcript": {
7
      "provider": {
8
        "deepgram": {
9
          "model": "nova-3",
10
          "language": "en"
11
        }
12
      }
13
    }
14
  },
15
  "automatic_leave": {
16
    "everyone_left_timeout": 5
17
  }
18
}

Parameter reference

Tip: You can also pass audio_separate_streams nested inside recording_config:

1
"recording_config": {
2
  "audio_separate_streams": true
3
}

The top-level parameter takes precedence if both are set.

3) What happens during the meeting

Once the bot joins, it automatically:

• Captures each participant’s audio as a separate file.
• Records up to 16 concurrent speaker streams.
• Continues recording throughout the meeting — no configuration needed per participant.

The bot also continues to produce the standard mixed audio file (audio.wav) regardless of whether audio_separate_streams is enabled.

Note on platform behaviour: The mechanism for capturing per-participant audio differs between Zoom and Google Meet and affects the isolation level of each file. See Section 7 for details.

4) Retrieve per-participant audio streams

After the bot leaves and audio processing completes, call:

$
curl -X GET "https://api.meetstream.ai/api/v1/bots/<BOT_ID>/get_audio_streams" \
>
  -H "Authorization: Token <YOUR_API_KEY>"

Response when processing is complete

1
{
2
  "bot_id": "f923cd21-da86-4d77-b37b-0707d37751c8",
3
  "audio_status": "Success",
4
  "audio_streams_available": true,
5
  "participants": [
6
    {
7
      "participant_name": "John Doe",
8
      "streams": [
9
        {
10
          "stream_id": "JohnDoe_abc123",
11
          "segments": [
12
            {
13
              "segment_index": 0,
14
              "url": "https://s3.amazonaws.com/...?X-Amz-Signature=...",
15
              "filename": "John_Doe_abc123_0.webm",
16
              "duration_seconds": 125.5,
17
              "sample_rate": 48000,
18
              "channels": 1,
19
              "codec": "opus"
20
            }
21
          ]
22
        }
23
      ]
24
    },
25
    {
26
      "participant_name": "Jane Smith",
27
      "streams": [
28
        {
29
          "stream_id": "JaneSmith_def456",
30
          "segments": [
31
            {
32
              "segment_index": 0,
33
              "url": "https://s3.amazonaws.com/...?X-Amz-Signature=...",
34
              "filename": "Jane_Smith_def456_0.webm",
35
              "duration_seconds": 118.3,
36
              "sample_rate": 48000,
37
              "channels": 1,
38
              "codec": "opus"
39
            }
40
          ]
41
        }
42
      ]
43
    }
44
  ],
45
  "summary": {
46
    "total_participants": 2,
47
    "total_segments": 2
48
  }
49
}

Response when processing is still in progress

1
{
2
  "audio_status": "in_progress",
3
  "message": "Bot is still in the meeting. Audio streams will be available after the bot leaves."
4
}

HTTP status 202 is returned when the bot has not yet left the meeting. Poll again after the bot exits.

Response when no audio streams are available

1
{
2
  "bot_id": "f923cd21-da86-4d77-b37b-0707d37751c8",
3
  "audio_status": "Success",
4
  "audio_streams_available": false,
5
  "message": "No per-participant audio streams available for this bot.",
6
  "participants": []
7
}

This is returned when audio_separate_streams was not enabled, or the meeting ended before any speech was detected.

5) Download the audio files

Each segment in the response contains a url field — a presigned S3 URL that allows direct download without additional authentication.

$
# Download a participant's audio
>
curl -o "John_Doe.webm" "<PRESIGNED_URL_FROM_RESPONSE>"

Important: Presigned URLs expire after 10 minutes. If a URL has expired, call get_audio_streams again to get fresh URLs.

File format

6) Understanding segments

Each participant has one segment (segment_index: 0) covering the full duration of their speech in the meeting. Silence gaps between speech periods are preserved with actual silence, so the file’s timeline aligns with the real meeting timeline.

Use duration_seconds to determine how long a participant was speaking.

7) Per-participant audio by platform

The quality of speaker isolation differs by platform due to how each platform delivers audio.

Zoom produces the cleanest per-participant files. Google Meet files contain the meeting’s mixed audio during the periods when that participant was the active speaker.

8) Using both mixed and per-participant audio

Per-participant audio and the standard mixed audio are always captured simultaneously. You do not need to choose one or the other.

1
{
2
  "meeting_link": "<MEETING_LINK>",
3
  "audio_separate_streams": true
4
}

This produces:

• A mixed audio WAV (all participants combined) — retrieve via the Get Bot Audio endpoint (/api/v1/bots/<BOT_ID>/get_audio).
• Per-participant WebM files — retrieve via the Get Audio Streams endpoint (/api/v1/bots/<BOT_ID>/get_audio_streams).

9) Using per-participant audio with per-participant video

Both flags can be enabled together:

1
{
2
  "meeting_link": "<MEETING_LINK>",
3
  "audio_separate_streams": true,
4
  "video_separate_streams": true
5
}

This produces separate audio and video files per participant. The files are not muxed together — audio and video are delivered as independent files. Match them by participant_name across the two API responses.

10) Webhook notifications

If you have webhooks configured, you will receive an audio.processed event when audio processing (including per-participant stream generation) completes. Poll get_audio_streams until audio_streams_available is true if you prefer polling over webhooks.

11) Troubleshooting

• audio_streams_available: false with audio_status: "Success"?

  • Confirm that audio_separate_streams: true was set when the bot was created.
  • The meeting may have ended before any speech was detected.

• Missing a participant’s audio?

  • The bot captures up to 16 concurrent speaker streams. Meetings with more than 16 active speakers may result in some participants not being captured.
  • Participants who never spoke will not appear in the response.

• Getting status in_progress?

  • The bot is still in the meeting. Audio streams are generated after the bot exits. Wait for the bot to leave and poll again.

• Presigned URL returns 403 Forbidden?

  • The URL has expired (10-minute lifetime). Call get_audio_streams again for fresh URLs.

• Audio file sounds like the whole meeting, not just one person?

  • This is expected on Google Meet — see Section 7. The file contains the meeting audio during that participant’s active speaking windows. On Zoom, files are fully isolated.