Delete transcript
Erases the transcribed text, the words and the stored audio. The usage record itself stays, since it is what the invoice for the period is built from, but the content is gone and cannot be recovered.
Erases the transcribed text, the words and the stored audio. The usage record itself stays, since it is what the invoice for the period is built from, but the content is gone and cannot be recovered.
Authorization
bearerAuth API key (tk_...)
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/transcripts/string"{ "data": { "id": "string", "deleted": true }}Get transcript GET
Read this until `status` becomes `done` (text in `text`, word timings in `words`, cost in `cost`), `failed` (reason in `error`) or `canceled`. **Prefer `?wait=30` over a polling loop**: the response is held until the transcript finishes, and comes back immediately when it does. While it is still `processing`, the response carries `Retry-After` with the interval worth waiting before asking again. For many transcripts at once, `webhookUrl` on creation is still the cheaper path: one delivery per job instead of one connection per job.
Cancel transcript POST
Stops a transcript that is still `processing` and returns it with `status: "canceled"`. **Billing**: a canceled transcript is never charged, and the credit it was holding (`reserved` in `GET /v1/balance`) is released immediately. **Timing**: cancelling is about the charge, not about the machine. Audio already on a GPU runs to the end of its current work and the result is discarded; nothing about it reaches you or your invoice. A transcript that already reached `done`, `failed` or `canceled` returns `409`: those states are terminal, and the one that completed was already charged. If you passed a `webhookUrl`, the cancellation is delivered to it like any other ending.