Skip to main content

Overview

Export session conversation data from the Sessions view in Dashboard as CSV or JSON. Supported formats: csv, json
Row model: One row per user-facing message (user_query, assistant_response, system_continuation)
Hard limit: 10,000 rows per export request
If the export query would exceed 10,000 rows, the API returns:
Use filters (date range, user, last activity, evaluation rating) to reduce the result set.

Export Columns

The sessions export includes:
  • session_id
  • user_id
  • session_created_at
  • message_sequence (re-numbered per session for exported rows only)
  • message_type
  • message_content
  • message_created_at
  • evaluation_rating
  • evaluation_comment

Message Type Descriptions

The sessions export includes only user-facing message types:
  • user_query: A direct user question or prompt submitted in chat.
  • system_continuation: A user-triggered continuation event (for example, after completing an interaction step) that continues the same conversational turn.
  • assistant_response: The AI assistant response payload. In exports, this is stored in message_content as a serialized JSON object (schema below).

assistant_response Message Content Schema

For rows where message_type = "assistant_response", message_content is stored as a JSON object serialized to string. The canonical schema is:
guidance_text is required; all other fields are optional and appear only when relevant to the response.

Example assistant_response in JSON Export