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

# Delete an assistant

> Deleting is quiet: you get a 204 even if that id never existed, so a success is not proof anything was there. Every published version goes with it. Campaigns keep the now-dangling `assistantId`, and a running one pauses itself at its next dial with `statusMessage: "Paused: assistant version not found"`. The assistant's session list stops resolving, so pull the call history before you delete.



## OpenAPI

````yaml /voice-agents/api-reference/openapi.yaml delete /realtime-assistants/{realtimeAssistantId}
openapi: 3.1.0
info:
  title: UpliftAI Voice Agents API
  version: '1.0'
  description: >-
    Build voice assistants, start conversations on the web or the phone, run
    calling campaigns, and receive outcomes by webhook. All endpoints take a
    bearer API key unless noted otherwise.
servers:
  - url: https://api.upliftai.org/v1
security:
  - apiKey: []
tags:
  - name: Assistants
  - name: Authoring an assistant
  - name: Starting a conversation
  - name: Sessions & call records
  - name: Campaigns
  - name: Campaign outcomes
  - name: Contacts
  - name: Google Sheet sources
  - name: Integrations & delivery health
paths:
  /realtime-assistants/{realtimeAssistantId}:
    delete:
      tags:
        - Assistants
      summary: Delete an assistant
      description: >-
        Deleting is quiet: you get a 204 even if that id never existed, so a
        success is not proof anything was there. Every published version goes
        with it. Campaigns keep the now-dangling `assistantId`, and a running
        one pauses itself at its next dial with `statusMessage: "Paused:
        assistant version not found"`. The assistant's session list stops
        resolving, so pull the call history before you delete.
      operationId: deleteRealtimeAssistant
      parameters:
        - name: realtimeAssistantId
          in: path
          required: true
          schema:
            type: string
            format: uuid
          example: cc66dfda-2af8-4f4a-9f5f-a56adfa151de
      responses:
        '204':
          description: Empty body.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '409':
          $ref: '#/components/responses/AssistantBusy'
components:
  responses:
    Unauthorized:
      description: A bearer key was sent but is not recognized.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            message: invalid authorization
            error: Unauthorized
            statusCode: 401
    Forbidden:
      description: No API key sent, or the key lacks permission for this resource.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            message: Forbidden resource
            error: Forbidden
            statusCode: 403
    AssistantBusy:
      description: >-
        A save, build or publish holds the assistant. Nothing was changed. Retry
        in a moment.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            message: The realtime assistant is being modified, try again shortly
            error: Conflict
            statusCode: 409
  schemas:
    Error:
      type: object
      properties:
        message:
          description: >-
            One message per failed field for validation errors, a single string
            otherwise.
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        error:
          type: string
        statusCode:
          type: integer
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: Project API key (`sk_api_…`).

````