> ## Documentation Index
> Fetch the complete documentation index at: https://docs.instaview.sk/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Call Attempt

> Cancels and deletes a specific call attempt. Blocked for ONLINE conversations.

<Info>
  `DELETE /interviews/{id}/call-attempts/{attemptId}` is a permanent alias of this endpoint and keeps working unchanged, with the same scopes and the same response. See [Resource names](/api-reference/introduction#resource-names).
</Info>

Cancels and permanently deletes a specific call attempt.

<Warning>
  **ONLINE conversations**: managing individual call attempts is forbidden on an `ONLINE` conversation.
</Warning>

## Overview

Deleting a call attempt removes it from the conversation's history, and cancels it if it was scheduled for the future.

## Constraints

* **In-progress protection**: as with rescheduling, deleting an attempt that is `IN_PROGRESS` is blocked.
* **The conversation survives**: deleting attempts does not delete the conversation. To remove the conversation and all its data, use [Delete Conversation](/api-reference/conversations/delete-conversation).

<Info>
  **Use case**: clearing failed or redundant attempts out of a conversation's history, or cancelling a pending retry that is no longer wanted.
</Info>

## Webhooks

This endpoint emits **no webhook**. It cancels a single call attempt without changing the conversation's own status, so no conversation-level lifecycle event applies — in particular, no [`conversation.cancelled`](/guides/webhooks#conversation-cancelled-payload) is sent.

<Warning>
  Deleting the **last remaining scheduled attempt** leaves the conversation `SCHEDULED` with no
  future call queued, and emits no event. If your system treats a conversation as open until a
  terminal event arrives, either follow this call with [Delete
  Conversation](/api-reference/conversations/delete-conversation), or schedule a replacement with
  [Invoke New Call Attempt](/api-reference/conversations/invoke-call-attempt).
</Warning>


## OpenAPI

````yaml DELETE /conversations/{id}/call-attempts/{attemptId}
openapi: 3.0.0
info:
  title: InstaView API
  description: |-
    InstaView API Documentation

    ## Authentication

    All endpoints require API key authentication using Bearer token:
    ```
    Authorization: Bearer sk_your_api_key_here
    ```

    ## API Key Management

    The API Key module provides comprehensive key management for:
    - **Direct Client Keys**: Company-scoped keys for your applications
    - **ATS Partner Keys**: Resource-scoped keys for ATS integrations

    ### Key Features
    - HMAC-SHA256 hashing for API key storage
    - Configurable rate limiting
    - Comprehensive audit logging
    - Company-level isolation
    - Resource scoping for ATS partners
  version: 1.0.0
  contact: {}
servers:
  - url: https://api.instaview.sk
    description: Production API Gateway
security: []
tags: []
paths:
  /conversations/{id}/call-attempts/{attemptId}:
    delete:
      tags:
        - Conversations
      summary: Delete call attempt
      description: >-
        Cancels and deletes a specific call attempt. Blocked for ONLINE
        conversations.
      operationId: PublicInterviewsController_deleteCallAttempt_v1
      parameters:
        - name: id
          required: true
          in: path
          schema:
            type: string
            format: uuid
        - name: attemptId
          required: true
          in: path
          schema:
            type: string
            format: uuid
        - name: companyId
          required: false
          in: query
          description: >-
            Required for ATS API keys to specify which company to access.
            Ignored for standard company API keys.
          schema:
            type: string
      responses:
        '204':
          description: Call attempt deleted successfully
      security:
        - bearer: []
components:
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
      description: API key for authentication using Bearer scheme

````