Overview
CommBox supports recording for WebRTC video calls, allowing organizations to capture, store, and retrieve video conversations for operational, compliance, training, and quality assurance purposes.
When a recording is completed, the system automatically creates a dedicated activity entry linked to the relevant object, making recordings accessible through the existing Activities API infrastructure.
Recording Activity Type
| Activity Type | Description |
|---|---|
| activityType=27 | WebRTC Video Call Recording |
This activity is automatically generated once the recording process finishes successfully.
Retrieving Recordings via API
Recordings can be retrieved using the existing Activities endpoint:
GET /objects/{objectId}/activities?activityType=27
The endpoint returns all recording-related activities associated with the specified object.
Response Metadata
Each recording activity includes detailed metadata about the recorded session.
Example Response
{
"activityType": 27,
"recordingType": "video",
"recordingUrl": "https://s3.amazonaws.com/recordings/example.mp4",
"duration": 542,
"timestamp": "2026-05-13T09:14:22Z",
"fileSize": 104857600
}
Metadata Fields
| Field | Description |
|---|---|
| recordingUrl | Full S3 URL or presigned URL to access the recording file |
| duration | Total call duration in seconds |
| recordingType | Recording type. Current value: "video" |
| timestamp | Timestamp indicating when the recording was created |
| fileSize | Recording file size in bytes |
Recording Storage & Access
The recordingUrl field may contain either:
• A direct S3 file URL
• A presigned URL with temporary secure access permissions
This enables flexible integration with external storage policies and secure file delivery mechanisms.
Common Use Cases
Organizations can use WebRTC call recordings for:
• Quality assurance and agent evaluation
• Compliance and audit requirements
• Training and onboarding
• Customer dispute resolution
• Operational monitoring and review
Notes
• Recording activities are created only after the recording process completes successfully.
• Video recordings are linked to the relevant object activity timeline.
• Existing API authentication and permission models fully apply to recording retrieval.