> ## 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 Conversation Variables

> Retrieve variables from a specific conversation.



## OpenAPI

````yaml /en/api-reference/openapi_chatflow.json get /conversations/{conversation_id}/variables
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}/variables:
    get:
      tags:
        - Conversations
      summary: List Conversation Variables
      description: Retrieve variables from a specific conversation.
      operationId: getAdvancedConversationVariables
      parameters:
        - name: conversation_id
          in: path
          required: true
          description: Conversation ID.
          schema:
            type: string
        - name: user
          in: query
          required: false
          description: The 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: variable_name
          in: query
          required: false
          description: Filter variables by a specific name.
          schema:
            type: string
            minLength: 1
            maxLength: 255
      responses:
        '200':
          description: Successfully retrieved conversation variables.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConversationVariablesResponse'
              examples:
                conversationVariables:
                  summary: Response Example
                  value:
                    limit: 20
                    has_more: false
                    data:
                      - id: a1b2c3d4-5678-90ab-cdef-1234567890ab
                        name: user_preference
                        value_type: string
                        value: dark_mode
                        description: User preference setting
                        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:
    ConversationVariablesResponse:
      type: object
      properties:
        limit:
          type: integer
          description: Number of items per page.
        has_more:
          type: boolean
          description: Whether there is a next page.
        data:
          type: array
          description: List of conversation variables.
          items:
            $ref: '#/components/schemas/ConversationVariableItem'
    ConversationVariableItem:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: Variable ID.
        name:
          type: string
          description: Variable name.
        value_type:
          type: string
          description: >-
            Variable value type. Possible values: `string`, `number`, `object`,
            `secret`, `file`, `boolean`, `array[any]`, `array[string]`,
            `array[number]`, `array[object]`, `array[file]`, `array[boolean]`.
        value:
          type: string
          description: Variable value (can be a JSON string for complex types).
        description:
          type: string
          description: Variable description.
        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.**

````