> ## Documentation index
> Fetch the complete documentation index at: https://dify-docs.docs7.io/llms.txt
> Ask it with GET https://dify-docs.docs7.io/ask?q=<keywords or question>. Short keywords rank best.
> Use these to discover all available pages before exploring further.

# Delete Conversation

> **Available for**: Chatflow, Agent, Chatbot, Legacy Agent apps.

Deletes a conversation.

`DELETE /conversations/{conversation_id}`

## OpenAPI

````yaml en/api-reference/openapi_service.json delete /conversations/{conversation_id}
openapi: 3.0.1
info:
  description: REST API for Dify applications and knowledge bases. Application
    endpoints authenticate with an app API key; knowledge endpoints authenticate
    with a dataset API key.
  title: Dify Service API
  version: 1.0.0
servers:
  - description: Base URL of the Dify Service API. For self-hosted deployments,
      replace it with your own API base URL.
    url: https://{api_base_url}
    variables:
      api_base_url:
        default: api.dify.ai/v1
        description: Host and path of the API base URL, without the `https://` prefix.
security:
  - ApiKeyAuth: []
tags:
  - description: Operations related to chat messages and interactions.
    name: Chat Messages
  - description: File upload and preview operations.
    name: Files
  - description: Operations related to end user information.
    name: End Users
  - description: User feedback operations.
    name: Feedback
  - description: Operations related to managing conversations.
    name: Conversations
  - description: Text-to-Speech and Speech-to-Text operations.
    name: Audio
  - description: Operations to retrieve application settings and information.
    name: Applications
  - description: Operations related to managing annotations for direct replies.
    name: Annotations
  - description: Endpoints for resuming paused workflows that require human input.
    name: Human Input
  - description: Operations for executing and managing workflows.
    name: Workflow Runs
  - description: Operations related to text generation and completion.
    name: Completion Messages
  - description: Operations for managing knowledge bases, including creation,
      configuration, and retrieval.
    name: Knowledge Bases
  - description: Operations for creating, updating, and managing documents within a
      knowledge base.
    name: Documents
  - description: Operations for managing document chunks and child chunks.
    name: Chunks
  - description: Operations for managing knowledge base metadata fields and document
      metadata values.
    name: Metadata
  - description: Operations for managing knowledge base tags and tag bindings.
    name: Tags
  - description: Operations for retrieving available models.
    name: Models
  - description: Operations for managing and running knowledge pipelines, including
      datasource plugins and pipeline execution.
    name: Knowledge Pipeline
paths:
  /conversations/{conversation_id}:
    delete:
      description: |-
        **Available for**: Chatflow, Agent, Chatbot, Legacy Agent apps.

        Deletes a conversation.
      operationId: deleteConversation
      parameters:
        - description: ID of the conversation to delete. Get conversation IDs from [List
            Conversations](/en/api-reference/conversations/list-conversations).
          in: path
          name: conversation_id
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            examples:
              deleteExample:
                summary: Request Example
                value:
                  user: abc-123
            schema:
              properties:
                user:
                  description: End-user identifier, defined by your app and unique within it. See
                    [End User
                    Identity](/en/api-reference/guides/end-user-identity).
                  type: string
              type: object
        description: A JSON body is always required, even when `user` is omitted; send
          `{}` in that case.
        required: true
      responses:
        "204":
          description: Conversation deleted successfully. No content returned.
        "400":
          content:
            application/json:
              examples:
                not_chat_app:
                  summary: not_chat_app
                  value:
                    code: not_chat_app
                    message: Please check if your app mode matches the right API route.
                    status: 400
          description: "`not_chat_app` : App mode does not match the API route."
        "404":
          content:
            application/json:
              examples:
                conversation_not_exists:
                  summary: not_found
                  value:
                    code: not_found
                    message: Conversation Not Exists.
                    status: 404
          description: "`not_found` : Conversation does not exist."
      summary: Delete Conversation
      tags:
        - Conversations
      x-mint:
        href: /en/api-reference/conversations/delete-conversation
        metadata:
          sidebarTitle: Delete Conversation
          title: Delete Conversation
components:
  securitySchemes:
    ApiKeyAuth:
      bearerFormat: API_KEY
      description: >-
        Every request authenticates with an API key: `Authorization: Bearer
        {API_KEY}`. App endpoints take an app API key; knowledge endpoints take
        a knowledge base API key ([Get
        Started](/en/api-reference/guides/get-started)).


        Keep keys server-side; never embed them in client code. Requests with a
        missing or invalid key fail with HTTP `401` (`unauthorized`).
      scheme: bearer
      type: http
````