> ## Documentation Index
> Fetch the complete documentation index at: /llms.txt
> Use this file to discover all available pages before exploring further.

# List conversations

> Returns your conversations, newest first. Filter with `status`, or with `customerId` for one customer's.
Each item names its `customerId`.

Required scope: `conversations:read`.




## OpenAPI

````yaml /openapi.yaml get /conversations
openapi: 3.1.0
info:
  title: Cerium API
  version: 1.0.0
  description: |
    Send your customers and their conversations to Cerium from your own backend.
    Every request is authenticated with an API key.
servers:
  - url: https://api.usecerium.com/v1
    description: Production
security:
  - apiKey: []
tags:
  - name: Customers
  - name: Conversations
  - name: Messages
paths:
  /conversations:
    get:
      tags:
        - Conversations
      summary: List conversations
      description: >
        Returns your conversations, newest first. Filter with `status`, or with
        `customerId` for one customer's.

        Each item names its `customerId`.


        Required scope: `conversations:read`.
      operationId: listConversations
      parameters:
        - name: status
          in: query
          description: Only conversations that are open or closed.
          schema:
            $ref: '#/components/schemas/ConversationStatus'
        - name: customerId
          in: query
          description: Only this customer's conversations.
          schema:
            type: string
            maxLength: 40
          example: prt_8271
        - $ref: '#/components/parameters/Page'
        - $ref: '#/components/parameters/Limit'
      responses:
        '200':
          description: A page of conversations.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConversationList'
        '400':
          $ref: '#/components/responses/Invalid'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '429':
          $ref: '#/components/responses/RateLimited'
components:
  schemas:
    ConversationStatus:
      type: string
      enum:
        - open
        - closed
    ConversationList:
      type: object
      properties:
        message:
          type: string
        status:
          type: string
          example: success
        data:
          type: array
          items:
            $ref: '#/components/schemas/ConversationSummary'
        meta:
          $ref: '#/components/schemas/PageMeta'
    ConversationSummary:
      type: object
      properties:
        id:
          type: string
          example: thr_01k9z3m4q8
        customerId:
          type:
            - string
            - 'null'
          example: prt_8271
        status:
          $ref: '#/components/schemas/ConversationStatus'
        lastMessageAt:
          type:
            - string
            - 'null'
          format: date-time
        createdAt:
          type: string
          format: date-time
    PageMeta:
      type: object
      properties:
        totalItems:
          type: integer
          example: 134
        itemCount:
          type: integer
          example: 20
        itemsPerPage:
          type: integer
          example: 20
        totalPages:
          type: integer
          example: 7
        currentPage:
          type: integer
          example: 1
    Error:
      type: object
      description: >
        `message` is always present. `code` is a stable identifier for specific
        errors you may want to handle in code.

        A validation error has a `message` that is a list of everything to fix.
      properties:
        code:
          type: string
          description: A stable identifier you can match on.
        message:
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: integer
        error:
          type: string
      required:
        - message
  parameters:
    Page:
      name: page
      in: query
      schema:
        type: integer
        minimum: 1
        default: 1
    Limit:
      name: limit
      in: query
      schema:
        type: integer
        minimum: 1
        maximum: 100
        default: 20
  responses:
    Invalid:
      description: The request is not valid. `message` says what to fix.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            statusCode: 400
            error: Bad Request
            message:
              - email must be an email
    Unauthorized:
      description: The key is missing or not valid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            statusCode: 401
            message: Authentication token is missing.
    Forbidden:
      description: The key does not have the scope this call needs.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            statusCode: 403
            message: This key cannot do that.
    RateLimited:
      description: Too many requests. Wait, then try again.
      headers:
        Retry-After:
          description: Seconds to wait before trying again.
          schema:
            type: integer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >
        Your API key, sent as `Authorization: Bearer <key>`. Create keys in the
        Cerium dashboard.

        Keep them on your servers only.

````