Vobiz Logo
Vobiz
|API Documentation
Console
← Back to Recording

Stop Conference Recording

Stop an active conference recording and retrieve the recording file URL.

This API allows you to stop an active conference recording. Once stopped, the recording is finalized and becomes available for download.

Authentication Required:

  • • X-Auth-ID: Your account ID (e.g., {Auth_ID})
  • • X-Auth-Token: Your account Auth Token
  • • Content-Type: application/json

Processing Time: After stopping, the recording file may take a few moments to be fully processed and available at the provided URL. The file will remain accessible according to your account retention policy.

Note: If no recording is active for the specified conference, this call will return an error. Recordings are also automatically stopped when a conference ends.

HTTP Request

DELETEhttps://api.vobiz.ai/api/v1/Account/{auth_id}/Conference/{conference_name}/Record/

Request Body

JSON
{}

No request body parameters required. Send an empty JSON object or omit the body.

Response

Response - 204 No Content
HTTP Status Code: 204

Success: A 204 No Content status indicates the recording was successfully stopped. The recording file will be available at the URL provided when you started the recording, or via the recording_callback_url if configured.

Examples

Stop Conference Recording

cURL Request
curl -X DELETE https://api.vobiz.ai/api/v1/Account/{auth_id}/Conference/MyConf/Record/ \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

JavaScript Example - Stop Recording

JavaScript Example
async function stopRecording(conferenceName) {
  const response = await fetch(
    `https://api.vobiz.ai/api/v1/Account/{auth_id}/Conference/${conferenceName}/Record/`,
    {
      method: 'DELETE',
      headers: {
        'X-Auth-ID': '{auth_id}',
        'X-Auth-Token': '{access_token}'
      }
    }
  );

  if (response.status === 204) {
    console.log('Recording stopped successfully');
    // Recording file will be available via callback URL
    // or can be retrieved from your recording storage
  }
}

stopRecording('MyConf');

Best Practices:

  • • Download recordings immediately to your own storage
  • • Store recording_id in your database for future reference
  • • Implement retry logic for download failures
  • • Verify recording duration matches expected conference length

Callback Notification: If you configured a recording_callback_url when starting the recording, you'll receive a POST request with the recording details once processing is complete.

Start Recording
Integrations