# List the sessions

Returns a paginated list of all available chat sessions.
    
    The response includes:
    - List of session summaries
    - Pagination information
    - Total count of returned sessions
    
    Each session summary contains:
    - session_id: Unique identifier for the session
    - checkpoint_id: Internal reference ID
    - short_name: Brief description based on first message
    
    Use the query parameters to navigate through pages:
    - before: Get sessions before this session ID
    - limit: Number of sessions per page (1-50)
    
    Sessions are ordered by most recent first.
    Empty sessions (no messages) are automatically filtered out.

Endpoint: GET /core/v1/sessions
Version: v1
Security: APIKeyHeader

## Query parameters:

  - `before` (any)
    Filter sessions before this session id

  - `limit` (integer)
    Limit the number of sessions to return

## Response 200 fields (application/json):

  - `sessions` (array, required)
    List of available sessions

  - `sessions.session_id` (string, required)
    The ID of the session.

  - `sessions.checkpoint_id` (string, required)
    The ID of the checkpoint.

  - `sessions.short_name` (string, required)
    The short name of the session.

  - `sessions.created_at` (string, required)
    The creation timestamp of the session in UTC.

## Response 401 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 403 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 422 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 500 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available