DELETE /calls/{callid}/recordings/{uniqueid}/{recordingid}
Delete one recording file of a leg
| Scope | recordings:delete |
| Role permission | Account Owner role only — any other role is 403 permission_denied, whatever the scopes |
| Cost | Free |
PERMANENT. The audio is destroyed and there is no recovery — not through this API, not in the portal. Every delete is written to the account's audit log.
The same rules as the portal's delete, plus the rules that decide whether you may hear the recording at all:
- Account Owner only. For an API key, the key's run-as user must be
on the Account Owner role; for an OAuth token, the user who approved
the app. Holding
recordings:deleteis not enough on its own. - You must be able to see it. The leg must appear in your own
GET /calls/{callid}/recordingslisting, so the role's call-report access and an API key's phone number limits apply. A leg you cannot see is404, the same answer as one that does not exist. - Accounts with sensitive-content re-verification on get no API access to recordings, so nothing can be deleted over the API there.
recordings:read does not include deleting, and recordings:delete
does not include reading — ask for both if you list before deleting.
Deletes only the file named by recordingid. Any other file on the
same leg is kept. The id must match a file on that leg in your listing,
or the answer is 404 — this never falls back to another file.
Path parameters
| Name | Type | Required | Example | Description |
|---|---|---|---|---|
callid | string | yes | 1754489201.884213 | The call id from call history, reports or a call webhook — a unix timestamp, a dot, and a sequence number. A malformed id is a 400 that names the expected shape, not a 404. |
uniqueid | string | yes | 1754489201.884213 | The leg identifier, from uniqueId in the list response. |
recordingid | integer | yes | 2 | The file to delete, from recordingId in the list response. A positive whole number; anything else is 400. |
Responses
204
Deleted. No body.
Errors
| Status | Meaning |
|---|---|
400 | invalid_request — a missing or malformed field, an unknown enum value, or an unknown field in the body. Nothing was charged. |
401 | unauthenticated — no credential, or one that is invalid, revoked or expired. The WWW-Authenticate header names the scope the endpoint wanted. |
403 | Two different failures share this status; the type field tells them apart — insufficient_scope (the credential lacks the scope) or permission_denied (the scope is fine, but the user's role lacks the permission). |
404 | not_found — no such object, or it is not this account's. The two are deliberately indistinguishable. |
500 | internal_error — something failed on our side, not with your request. Safe to retry. |
See Errors for the full catalog and what to do about each.
Example
curl -X DELETE 'https://api.account.telebroad.com/api/public/v1/calls/1754489201.884213/recordings/1754489201.884213/2' \
-H "Authorization: Bearer $TB_KEY"