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

# Rename Conversation

> Rename a conversation or auto-generate a name. The conversation name is used for display on clients that support multiple conversations.



## OpenAPI

````yaml /en/api-reference/openapi_chatflow.json post /conversations/{conversation_id}/name
openapi: 3.0.1
info:
  title: Chatflow App API
  description: >-
    Chatflow applications support session persistence, allowing previous chat
    history to be used as context for responses. Chatflow apps use the
    `advanced-chat` mode, providing workflow-level streaming events for detailed
    execution tracking including node starts, finishes, iterations, and workflow
    lifecycle.
  version: 1.0.0
servers:
  - url: '{api_base_url}'
    description: >-
      The base URL for the Chatflow App API. Replace {api_base_url} with the
      actual API base URL provided for your application.
    variables:
      api_base_url:
        default: https://api.dify.ai/v1
        description: Actual base URL of the API
security:
  - ApiKeyAuth: []
tags:
  - name: Chatflows
    description: >-
      Operations for Chatflow apps, including chat messaging, workflow run
      details, and event streaming.
  - name: Files
    description: File upload and preview operations.
  - name: End Users
    description: Operations related to end user information.
  - name: Feedback
    description: User feedback operations.
  - name: Conversations
    description: Operations related to managing conversations.
  - name: TTS
    description: Text-to-Speech and Speech-to-Text operations.
  - name: Applications
    description: Operations to retrieve application settings and information.
  - name: Annotations
    description: Operations related to managing annotations for direct replies.
  - name: Human Input
    description: Endpoints for resuming paused workflows that require human input.
paths:
  /conversations/{conversation_id}/name:
    post:
      tags:
        - Conversations
      summary: Rename Conversation
      description: >-
        Rename a conversation or auto-generate a name. The conversation name is
        used for display on clients that support multiple conversations.
      operationId: renameAdvancedConversation
      parameters:
        - name: conversation_id
          in: path
          required: true
          description: Conversation ID.
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConversationRenameRequest'
            examples:
              renameExample:
                summary: Request Example
                value:
                  name: iPhone Specs Chat
                  user: abc-123
      responses:
        '200':
          description: Conversation renamed successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConversationListItem'
              examples:
                renamedConversation:
                  summary: Response Example
                  value:
                    id: 45701982-8118-4bc5-8e9b-64562b4555f2
                    name: iPhone Specs Chat
                    inputs:
                      city: San Francisco
                    status: normal
                    introduction: Welcome! How can I help you today?
                    created_at: 1705407629
                    updated_at: 1705411229
        '400':
          description: '`not_chat_app` : App mode does not match the API route.'
          content:
            application/json:
              examples:
                not_chat_app:
                  summary: not_chat_app
                  value:
                    status: 400
                    code: not_chat_app
                    message: Please check if your app mode matches the right API route.
        '404':
          description: '`not_found` : Conversation does not exist.'
          content:
            application/json:
              examples:
                conversation_not_exists:
                  summary: not_found
                  value:
                    status: 404
                    code: not_found
                    message: Conversation Not Exists.
components:
  schemas:
    ConversationRenameRequest:
      type: object
      description: Request body for renaming a conversation.
      required:
        - user
      properties:
        name:
          type: string
          description: >-
            The name of the conversation. Required when `auto_generate` is
            `false`.
        auto_generate:
          type: boolean
          default: false
          description: >-
            Automatically generate the conversation name. When `true`, the
            `name` field is ignored.
        user:
          type: string
          description: The user identifier.
    ConversationListItem:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: Conversation ID.
        name:
          type: string
          description: Conversation name.
        inputs:
          type: object
          additionalProperties: true
          description: Input variables for the conversation.
        status:
          type: string
          description: Conversation status. `normal` for active conversations.
        introduction:
          type: string
          description: Conversation introduction.
        created_at:
          type: integer
          format: int64
          description: Creation timestamp.
        updated_at:
          type: integer
          format: int64
          description: Last update timestamp.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: API_KEY
      description: >-
        API Key authentication. For all API requests, include your API Key in
        the `Authorization` HTTP Header, prefixed with `Bearer `. Example:
        `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API
        Key on the server-side, not shared or stored on the client-side, to
        avoid possible API-Key leakage that can lead to serious consequences.**

````