Skip to main content
DELETE
Delete conversation
DELETE /interviews/{id} is a permanent alias of this endpoint and keeps working unchanged, with the same scopes and the same response. See Resource names.
Permanently deletes a conversation and everything recorded with it. This action cannot be undone.

Overview

This endpoint removes a conversation and all of its data — transcripts, recordings, analyses — from your account. Use it for data hygiene, or to clear out test calls.

Use Cases

  • Drop what is no longer needed: conversations scheduled and then called off
  • Clean up test calls: remove test or development conversations from production
  • Data management: permanently remove a conversation and everything with it

Impact on Associated Data

Permanent Deletion: This action is irreversible. All associated data (transcripts, recordings, and analysis) will be permanently deleted.

Conversation States

A conversation can be deleted whatever its current status:

Scheduled Conversation Behavior

Deleting a scheduled conversation removes it from the processing queue, so the call is never placed. Its scheduled call attempts are marked CANCELLED and dequeued with it.

In-Progress Conversation Behavior

Deleting an in-progress conversation lets the live call run to its natural end. All post-call processing is skipped once it does.
When you delete an in-progress conversation:
  • The active phone call continues until it ends naturally
  • When the call ends, no post-call processing occurs:
    • No transcript generation
    • No analysis or scoring
    • No completion webhooks
  • Concurrency slots are released when the call ends
If you want the call’s data (transcript, analysis), wait for the conversation to complete before deleting it. Deleting one mid-call collects nothing at all.

Webhooks

Deletion emits no webhook, including no conversation.cancelled. Deleting removes the resource outright rather than cancelling it, and any of the conversation’s webhook deliveries still pending at that moment are cancelled as part of the same operation.
If you rely on a terminal event to close a conversation out in your own system, record the deletion at the point you issue this call — no event will arrive afterwards, and a subsequent GET /conversations/{id} returns 404.

Example Usage

Company Isolation

You can only delete conversations belonging to your API key’s company. Reaching for one from another company returns 403 Forbidden.

Required Scopes

This endpoint requires the delete:conversations scope (or its legacy alias delete:interviews). Ensure your API key has this scope enabled.

Error Scenarios

Conversations Resource Guide

Learn the conversation lifecycle

List Conversations

View a contact’s conversations

Get Conversation

Read it before you delete it

Create Conversation

Schedule a new call

Authorizations

Authorization
string
header
required

API key for authentication using Bearer scheme

Path Parameters

id
string<uuid>
required

Query Parameters

companyId
string

Required for ATS API keys to specify which company to access. Ignored for standard company API keys.

Response

200 - application/json

Conversation deleted successfully

id
string<uuid>
required

Id of the deleted resource

deleted
enum<boolean>
required

Always true; a failed delete answers with an error status

Available options:
true
Example:

true