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

# List the tickets behind a Sankey node/link

> Drill down into a conversation-flow Sankey: list the actual chat sessions (tickets) that flow through a clicked node or link.



## OpenAPI

````yaml get /impact-report/sankey/tickets
openapi: 3.1.0
info:
  title: OpenCX API
  description: >

    OpenCX is an AI-powered, all-in-one platform for customer support and
    outbound communications.


    Use this API to manage your OpenCX organization's AI agents, actions,
    conversations, contacts, and more.


    To get started, generate a new API key from the dashboard.


    ## Authentication

    All API endpoints require authentication using a Bearer token. You can
    generate an API key from your OpenCX dashboard.


    ## Rate Limiting

    API requests are rate limited to ensure fair usage. The current limits are:

    - 100 requests per minute for standard endpoints

    - 1000 requests per minute for streaming endpoints


    ## Error Handling

    The API uses standard HTTP status codes and returns detailed error messages
    in the response body.
  version: 1.0-beta
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: http://localhost:8080
    description: Development
  - url: https://api.open.cx
    description: Production
security:
  - bearerAuth: []
paths:
  /impact-report/sankey/tickets:
    get:
      summary: List the tickets behind a Sankey node/link
      description: >-
        Drill down into a conversation-flow Sankey: list the actual chat
        sessions (tickets) that flow through a clicked node or link. Pass the
        SAME dimensions/date/custom_data_key as getConversationSankey, plus a
        JSON-encoded `path` — one {layerIndex, bucket} constraint for a clicked
        node, two for a clicked link. Paginated via limit/offset. Chain into
        investigate_session on a returned ticket id to diagnose the "why".
      operationId: getConversationSankeyTickets
      parameters:
        - schema:
            type: string
          in: query
          name: dimensions
          required: true
          description: >-
            Ordered dimensions, 1–6, built left→right. Either a comma-separated
            key list ("replied_by,outcome") or a JSON array of {dimension,
            customDataKey} to give each custom-data column its own jsonb key,
            e.g.
            [{"dimension":"contact_custom_data","customDataKey":"tier"},{"dimension":"session_custom_data","customDataKey":"plan"}].
        - schema:
            type: string
          in: query
          name: path
          required: true
          description: >-
            JSON-encoded array of {layerIndex, bucket} constraints identifying
            the clicked target: 1 constraint = a clicked node, 2 = a clicked
            link. bucket may be an "Other (N)" label.
        - schema:
            type: string
          in: query
          name: custom_data_key
          required: false
          description: >-
            Fallback jsonb key for custom-data dimensions given via the CSV form
            (or when a JSON dimension omits its own customDataKey). Ignored
            where a dimension carries its own key.
        - schema:
            type: string
          in: query
          name: start_date
          required: false
          description: Start date in ISO 8601 format (defaults to 30 days ago)
        - schema:
            type: string
          in: query
          name: end_date
          required: false
          description: >-
            End date in ISO 8601 format; a date-only value covers the whole UTC
            day (defaults to now)
        - schema:
            default: 20
            type: integer
            minimum: 1
            maximum: 100
          in: query
          name: limit
          required: false
        - schema:
            default: 0
            type: integer
            minimum: 0
            maximum: 9007199254740991
          in: query
          name: offset
          required: false
      responses:
        '200':
          description: Default Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SankeyTicketsResDto'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDto'
components:
  schemas:
    SankeyTicketsResDto:
      $schema: https://json-schema.org/draft/2020-12/schema
      $id: '#/components/schemas/SankeyTicketsResDto'
      type: object
      properties:
        tickets:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
                format: uuid
                pattern: >-
                  ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
              ticketNumber:
                type: number
              channel:
                type: string
              aiClosureType:
                type:
                  - string
                  - 'null'
              mainStatus:
                type: string
              sentiment:
                type:
                  - string
                  - 'null'
              createdAt:
                type: string
              lastMessage:
                type:
                  - string
                  - 'null'
              contactName:
                type:
                  - string
                  - 'null'
              contactEmail:
                type:
                  - string
                  - 'null'
            required:
              - id
              - ticketNumber
              - channel
              - aiClosureType
              - mainStatus
              - sentiment
              - createdAt
              - lastMessage
              - contactName
              - contactEmail
            additionalProperties: false
        total:
          type: number
        hasMore:
          type: boolean
      required:
        - tickets
        - total
        - hasMore
      additionalProperties: false
    ErrorDto:
      type: object
      properties:
        statusCode:
          type: integer
        message:
          type: string
        error:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.