Recording

Record Google Meet and Teams meetings to your own Telnyx Storage bucket with recording_export. Use Storage to download, share, retain, and delete the resulting video.

Export a Recording to Storage

Set recording_export when creating the session:

{
  "meeting_url": "https://meet.google.com/abc-defg-hij",
  "idempotency_key": "recorded-planning-2026-11-10",
  "recording": true,
  "recording_view": "gallery_view",
  "recording_export": {
    "bucket": "meeting-recordings",
    "prefix": "weekly-planning"
  }
}

Request	Result
Omit `recording` and `recording_export`	No recording. Transcription remains separate.
Supply `recording_export`, omit `recording`	Recording enabled.
`recording: true` with `recording_export`	Recording enabled.
`recording: false` without a destination	Recording disabled.
`recording: true` without `recording_export`	Invalid request. Supply a destination bucket.
`recording: false` with `recording_export`	Invalid request.

recording_view accepts speaker_view (default), gallery_view, or speaker_view_no_sidebar. A layout does not enable recording by itself. These recording options apply to Google Meet and Teams. Recording options are fixed at creation; there are no start, pause, resume, or stop-recording actions. The bucket must already exist and be accessible to the authenticated organization/user. Do not send Storage credentials, organization IDs, region, or a destination key: the service resolves the region and generates the object key. prefix is optional, up to 256 characters, using letters, digits, /, _, ., and -. Empty, . and .. path segments are rejected; one trailing slash is normalized. Zoom rejects recording, recording_view, and recording_export with 422 unsupported_capability; omit those fields for Zoom. The session’s top-level recording field reports current activity. For Storage recordings, config.recording reports the creation-time intent. Neither proves that an exported file is ready.

Read Export Status

GET /v2/meeting_sessions/{id} includes data.recording_export. GET /v2/meeting_sessions/{id}/recordings returns the same reference at the top level:

{
  "data": [],
  "recording_export": {
    "type": "video",
    "bucket": "meeting-recordings",
    "region": "us-central-1",
    "key": "weekly-planning/recording.mp4",
    "bytes": 1048576,
    "status": "exported",
    "exported_at": "2026-11-03T12:00:00Z"
  }
}

The key above is illustrative; use the values returned for your session. recording_export can be null when recording is disabled or no customer export reference is available yet. It is not included in session list responses.

Status	Meaning
`pending`	Export is not ready. `bytes` and `exported_at` can be `null`.
`exported`	Upload has been verified. Download the object through Storage.
`failed`	Export failed terminally. Inspect the `recording.export_failed` event’s `reason`.

The data array is empty for Storage exports. Use recording_export.status to track completion. With MCP, read the export reference through get_session.recording_export. Exports emit recording.exported or recording.export_failed. These events are available through the event history, live stream, and configured webhook. Session termination and transcript finalization can happen before export completion. An export failure does not delete the transcript or artifacts.

Export Failure Reasons

recording.export_failed includes a reason. The failed export is terminal; retrying the status read does not restart the export. Preserve the session ID and returned reason when contacting support.

Reason	Meaning
`invalid_target`	The recording destination could not be used.
`invalid_media`	The captured media could not be exported as a valid recording.
`source_changed`	The recording changed while export was in progress.
`source_unavailable`	The captured recording was unavailable.
`too_large`	The recording exceeded the export size limit.
`storage_unavailable`	Storage could not complete the upload.
`object_conflict`	An object at the destination conflicted with the recording.
`verification_failed`	The uploaded object could not be verified.
`worker_lost`	Recording processing was interrupted before export completed.
`internal_error`	An unexpected export error occurred.

Once the status is exported, use the returned bucket, region, and key with Storage:

Download an object using your Storage credentials.
Create a presigned URL to share temporary access without sharing your API key.
Storage SDKs for programmatic access.

Retention and Deletion

The video belongs to your Storage bucket. Manage its retention and object locks through Storage, and delete the object when you no longer need it. Storage billing applies. Leaving or cancelling a meeting does not delete the exported file. The Meeting API’s recording_media deletion endpoint does not delete customer Storage objects. Deleting the video through Storage leaves the meeting session, transcript, events, and artifacts intact. Zoom recordings and existing Google Meet or Teams recordings held by the Meeting service remain available from GET /v2/meeting_sessions/{id}/recordings as temporary download links in data. Continue using the same session ID and endpoint; these recordings do not require a Storage bucket or migration. Refresh the result when a link expires. Choose the download method from the returned fields, rather than the meeting platform alone. See Collect Results and recording retention.

Meeting

Join a Meeting

During the Meeting

After the Meeting

Integration

API Reference

WebSocket

For AI Agents

Export a Recording to Storage

Read Export Status

Export Failure Reasons

Retention and Deletion

​Export a Recording to Storage

​Read Export Status

​Export Failure Reasons

​Download and Share

​Retention and Deletion

Export a Recording to Storage

Read Export Status

Export Failure Reasons

Download and Share

Retention and Deletion