Specala AIDocs
API Reference

Delete transcription

DELETE /transcriptions/{id} — permanently delete a transcription, its transcript text, AI reports and stored audio.

DELETE /transcriptions/{id}

Deletes one transcription — the same operation as deleting it in the app. The transcript text, AI reports and stored media are removed for every member of the workspace.

Irreversible — and gated by a key permission

Deleted content cannot be recovered. Only keys created with Allow deleting transcriptions can call this endpoint; other keys get 403 delete_scope_required. Your workspace role must also allow deleting — the same rules as in the app. See Authentication → Key permissions.

Path parameters

ParameterTypeDescription
idUUIDTranscription identifier — from List transcriptions or an upload response.

Request

curl -X DELETE https://app.specala.ai/api/v1/developer/transcriptions/3fa85f64-5717-4562-b3fc-2c963f66afa6 \
  -H "Authorization: Bearer sk_live_your_key_here"
import httpx

tid = "3fa85f64-5717-4562-b3fc-2c963f66afa6"
resp = httpx.delete(
    f"https://app.specala.ai/api/v1/developer/transcriptions/{tid}",
    headers={"Authorization": "Bearer sk_live_your_key_here"},
)
resp.raise_for_status()   # 204 No Content
const tid = "3fa85f64-5717-4562-b3fc-2c963f66afa6";
const res = await fetch(
  `https://app.specala.ai/api/v1/developer/transcriptions/${tid}`,
  {
    method: "DELETE",
    headers: { Authorization: "Bearer sk_live_your_key_here" },
  },
);
if (res.status !== 204) throw new Error(`HTTP ${res.status}`);

Deletion is deliberately not exposed as an MCP tool — a destructive operation shouldn't be one misunderstood prompt away. Use the REST endpoint from your own code, where the intent is explicit.

Response

204 No Content — the transcription is gone. Any later read of the same id returns 404, and it disappears from lists, exports and the app for all workspace members.

Deleting works in any status: a queued or processing transcription is stopped and cleaned up, and its reserved minutes are released.

Errors

StatusWhen
401Missing/invalid key, or key passed in the URL.
403Key without delete permission (delete_scope_required), plan without API access, or a workspace role that can't delete this transcription.
404No transcription with that id in this workspace — including one that's already deleted.
429Delete rate limit (30 requests / minute per key).

A repeated DELETE of the same id returns 404 — safe to treat as "already done". See Errors for the full reference.

On this page