---
title: "Delete WebRTC recording by ID"
method: DELETE
path: "/webrtc/1/recordings/{id}"
tags: ["channels", "webrtc-calls", "webrtc", "webrtc-recordings"]
---

# Delete WebRTC recording by ID

`DELETE /webrtc/1/recordings/{id}`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/webrtc/1/recordings/{id}`
- Auth: one of:
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`

This method allows deleting call recordings based on their ID.

## Path parameters

- `id` string, required

## Query parameters

- `location` 'SAO_PAULO' | 'BOGOTA' | 'FRANKFURT' | 'JOHANNESBURG' | 'JOHANNESBURG_1' | 'NEW_YORK' | 'PORTLAND' | 'MOSCOW' | 'SINGAPORE' | 'ISTANBUL' | 'KUALA_LUMPUR' | 'JAKARTA' | 'MUMBAI' | 'HONG_KONG_1' | 'HONG_KONG' | 'RIYADH' | 'CHENNAI'

## Response `200`

Success

- 6a67def771061fe877b7bafa26c22e83ef5c7b44e2a298a70b54e0ed657fe102RecordingResponse
  - `application` 5305ca722d832817d411146f95eba84c3530f174d0fd6b1f72c09c5c2fbb1063Application: Application data for the recording.
    - `type` 'WEBRTC', required
  - `recording` 6a67def771061fe877b7bafa26c22e83ef5c7b44e2a298a70b54e0ed657fe102Recording: Recording metadata
    - `composedFiles` 6a67def771061fe877b7bafa26c22e83ef5c7b44e2a298a70b54e0ed657fe102RecordingFile[]: Composed recording files.
      - `id` string: File ID.
      - `name` string: File name.
      - `fileFormat` 'PNG' | 'JPEG': File format.
      - `size` integer: File size in bytes.
      - `startTime` string, date-time: Date and time when the recording started.
      - `endTime` string, date-time: Date and time when the recording ended.
      - `creationTime` string, date-time: File creation time.
      - `duration` integer: File duration in seconds.
      - `location` 'UPLOADING' | 'UPLOADED' | 'HOSTED': Location of recording file after processing.
      - `customData` object: Client-defined data as key-value pairs, where both key and value are strings.
    - `callRecordings` 6a67def771061fe877b7bafa26c22e83ef5c7b44e2a298a70b54e0ed657fe102CallRecording[]: Call recording data.
      - `callId` string: Call identifier.
      - `endpoint` string: Call endpoint. Represents a caller for the inbound calls and a callee for the outbound calls.
      - `direction` 'INBOUND' | 'OUTBOUND': Call direction.
      - `status` 'SUCCESSFUL' | 'PARTIALLY_FAILED' | 'FAILED': Status of the call recording.
      - `reason` string: Reason for recording failure.
      - `files` 6a67def771061fe877b7bafa26c22e83ef5c7b44e2a298a70b54e0ed657fe102RecordingFile[]: Recording files.
        - `id` string: File ID.
        - `name` string: File name.
        - `fileFormat` 'PNG' | 'JPEG': File format.
        - `size` integer: File size in bytes.
        - `startTime` string, date-time: Date and time when the recording started.
        - `endTime` string, date-time: Date and time when the recording ended.
        - `creationTime` string, date-time: File creation time.
        - `duration` integer: File duration in seconds.
        - `location` 'UPLOADING' | 'UPLOADED' | 'HOSTED': Location of recording file after processing.
        - `customData` object: Client-defined data as key-value pairs, where both key and value are strings.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)