> ## 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.

# List Conversations

> Retrieve the conversation list for the current user, ordered by most recently active.



## OpenAPI

````yaml /en/api-reference/openapi_chatflow.json get /conversations
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:
    get:
      tags:
        - Conversations
      summary: List Conversations
      description: >-
        Retrieve the conversation list for the current user, ordered by most
        recently active.
      operationId: getAdvancedConversationsList
      parameters:
        - name: user
          in: query
          required: false
          description: User identifier.
          schema:
            type: string
        - name: last_id
          in: query
          required: false
          description: The ID of the last record on the current page (for pagination).
          schema:
            type: string
        - name: limit
          in: query
          required: false
          description: Number of records to return.
          schema:
            type: integer
            default: 20
            minimum: 1
            maximum: 100
        - name: sort_by
          in: query
          required: false
          description: Sorting field. Use '-' prefix for descending order.
          schema:
            type: string
            enum:
              - created_at
              - '-created_at'
              - updated_at
              - '-updated_at'
            default: '-updated_at'
      responses:
        '200':
          description: Successfully retrieved conversations list.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConversationsListResponse'
              examples:
                conversationsList:
                  summary: Response Example
                  value:
                    limit: 20
                    has_more: false
                    data:
                      - 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` : Last conversation does not exist (invalid `last_id`).'
          content:
            application/json:
              examples:
                last_conversation_not_exists:
                  summary: not_found
                  value:
                    status: 404
                    code: not_found
                    message: Last Conversation Not Exists.
components:
  schemas:
    ConversationsListResponse:
      type: object
      properties:
        limit:
          type: integer
          description: Number of items per page.
        has_more:
          type: boolean
          description: Whether there are more conversations.
        data:
          type: array
          description: List of conversations.
          items:
            $ref: '#/components/schemas/ConversationListItem'
    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.**

````