Skip to main content
DELETE
Delete interview
Permanently deletes an interview and its associated data. This action cannot be undone.

Overview

The delete interview endpoint permanently removes an interview and all its data (transcripts, recordings, analyses) from your account. This is useful for data hygiene or removing unwanted tests.

Use Cases

  • Remove Canceled Interviews: Clean up interviews that were scheduled but no longer needed
  • Clean Up Test Interviews: Remove test or development interviews from production
  • Data Management: Permanently remove interviews and all associated data

Impact on Associated Data

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

Interview States

Interviews can be deleted regardless of their current status:

Scheduled Interview Behavior

When you delete a scheduled interview, it is automatically removed from the processing queue. The call will not be initiated. Any scheduled call attempts are marked as CANCELLED and removed from the queue.

In-Progress Interview Behavior

Deleting an in-progress interview allows the active call to continue naturally until completion. However, all post-call processing will be skipped when the call ends.
When you delete an in-progress interview:
  • 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 need the interview data (transcripts, analysis), wait until the interview completes before deleting it. Deleting an in-progress interview prevents any data collection for that call.

Webhooks

Deletion emits no webhook, including no interview.cancelled. Deleting removes the resource outright rather than cancelling it, and any of the interview’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 the interview out in your own system, record the deletion at the point you issue this call — no event will arrive afterwards, and a subsequent GET /interviews/{id} returns 404.

Example Usage

Company Isolation

You can only delete interviews that belong to your API key’s company. Attempting to delete an interview from another company will result in a 403 Forbidden error.

Required Scopes

This endpoint requires the delete:interviews scope. Ensure your API key has this scope enabled.

Error Scenarios

Interviews Resource Guide

Learn about interview management and lifecycle

List Interviews

View all active interviews

Get Interview

Retrieve interview details before deletion

Create Interview

Schedule new interviews

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

Interview deleted successfully

statusCode
integer
required
Example:

200

message
string
required
Example:

"Success"

data
boolean
required
traceId
string | null