> ## Documentation Index
> Fetch the complete documentation index at: https://dify-6c0370d8-docs-agent-app-service-api.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# List Agent App Conversations

> Return Agent app conversations for the specified end user, ordered by most recently active.



## OpenAPI

````yaml /en/api-reference/openapi_agent.json get /conversations
openapi: 3.0.1
info:
  title: Agent App API
  description: >-
    Agent apps expose a streaming service API for production integrations. Use
    the API key created from the Agent app API Access page. Public service API
    requests use the returned API base URL and do not include the Agent ID in
    the path; the API key identifies the backing app.
  version: 1.0.0
servers:
  - url: https://{api_base_url}
    description: >-
      Base URL of the Agent App API. Use the Service API Base URL shown in the
      Agent app API Access page. For self-hosted deployments, replace it with
      your own 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:
  - name: Agent Messages
    description: Send Agent app messages and stop running tasks.
  - name: Agent Files
    description: Upload files for Agent app conversations.
  - name: Agent Conversations
    description: List Agent app conversations and conversation messages.
  - name: Agent App
    description: Retrieve Agent app parameters and metadata.
paths:
  /conversations:
    get:
      tags:
        - Agent Conversations
      summary: List Agent App Conversations
      description: >-
        Return Agent app conversations for the specified end user, ordered by
        most recently active.
      operationId: listAgentAppConversations
      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.**

````