> ## Documentation Index > Fetch the complete documentation index at: https://enterprise-docs.dify.ai/llms.txt > Use this file to discover all available pages before exploring further. # Rename Conversation > **Available for**: Chatflow, Chatbot, Agent apps. Renames a conversation, or auto-generates a name from its messages when `auto_generate` is `true`. The name is what clients display in a multi-conversation list. ## OpenAPI ````yaml /en/3.11.x/develop/api/openapi_service.json post /conversations/{conversation_id}/name openapi: 3.0.1 info: title: Dify Service API 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. version: 1.0.0 servers: - url: https://{api_base_url} description: >- Base URL of the Dify Service API. Replace it with your deployment's API endpoint. variables: api_base_url: default: api.example.com/v1 description: Host and path of the API base URL, without the `https://` prefix. security: - ApiKeyAuth: [] tags: - name: Chat Messages description: Operations related to chat messages and interactions. - 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: Audio 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. - name: Workflow Runs description: Operations for executing and managing workflows. - name: Completion Messages description: Operations related to text generation and completion. - name: Knowledge Bases description: >- Operations for managing knowledge bases, including creation, configuration, and retrieval. - name: Documents description: >- Operations for creating, updating, and managing documents within a knowledge base. - name: Chunks description: Operations for managing document chunks and child chunks. - name: Metadata description: >- Operations for managing knowledge base metadata fields and document metadata values. - name: Tags description: Operations for managing knowledge base tags and tag bindings. - name: Models description: Operations for retrieving available models. - name: Knowledge Pipeline description: >- Operations for managing and running knowledge pipelines, including datasource plugins and pipeline execution. paths: /conversations/{conversation_id}/name: post: tags: - Conversations summary: Rename Conversation description: >- **Available for**: Chatflow, Chatbot, Agent apps. Renames a conversation, or auto-generates a name from its messages when `auto_generate` is `true`. The name is what clients display in a multi-conversation list. operationId: renameConversation parameters: - name: conversation_id in: path required: true description: >- ID of the conversation to rename. Get conversation IDs from [List Conversations](/en/3.11.x/develop/api/conversations/list-conversations). 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. - `invalid_param` : `auto_generate` is `true` but the conversation has no messages to generate a name from. 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. no_messages: summary: invalid_param value: status: 400 code: invalid_param message: '' '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. properties: name: type: string description: New conversation name. Required unless `auto_generate` is `true`. auto_generate: type: boolean default: false description: >- Automatically generate the conversation name. When `true`, the `name` field is ignored. user: type: string description: >- End-user identifier, defined by your app and unique within it. See [End User Identity](/en/3.11.x/develop/api/guides/end-user-identity). 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: >- 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/3.11.x/develop/api/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`). ````