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

# Get Subchannels

> A subchannel is a further differentiation of the channel, and is - For emails, they are the mailboxes, e.g. support@enneo.ai and sales@enneo.ai - For chat, they are the chatbots, e.g. the chatbot on the website and the chatbot on the customer portal - For voice, they are the phone numbers, e.g. the phone number for support and the phone number for sales.




## OpenAPI

````yaml https://dev.enneo.dev/api/mind/docs/open-api get /settings/subchannel
openapi: 3.0.0
info:
  version: '1'
  title: enneo.MIND API
  description: This describes the API of enneo Mind, the main ticketing backend
  contact:
    name: enneo GmbH
    email: richard@enneo.ai
  license:
    name: Proprietary software
    url: https://enneo.ai
servers:
  - url: https://demo.enneo.ai/api/mind
    description: Production server, demo client
  - url: https://main.enneo.dev/api/mind
    description: Development main branch
  - url: http://localhost:8005/api/mind
    description: Local development server
security:
  - bearerAuth:
      - api
  - cookieAuth:
      - api
paths:
  /settings/subchannel:
    get:
      tags:
        - Settings
      summary: Get Subchannels
      description: >
        A subchannel is a further differentiation of the channel, and is - For
        emails, they are the mailboxes, e.g. support@enneo.ai and sales@enneo.ai
        - For chat, they are the chatbots, e.g. the chatbot on the website and
        the chatbot on the customer portal - For voice, they are the phone
        numbers, e.g. the phone number for support and the phone number for
        sales.
      operationId: getSubchannels
      parameters:
        - name: channels
          in: query
          required: false
          description: >-
            Filter by one or more channels. Accepts array format
            (?channels[]=email&channels[]=chat). Use 'all' to get subchannels
            from all channels (?channels[]=all). For backward compatibility,
            single channel parameter (?channel=email) is also supported.
          schema:
            type: array
            items:
              type: string
              enum:
                - all
                - email
                - chat
                - voice
                - phone
                - letter
                - internal
          style: form
          explode: true
        - name: channel
          in: query
          required: false
          deprecated: true
          description: >-
            (Deprecated) Filter by a single channel. Use 'channels' parameter
            instead for better flexibility. Use 'all' to get subchannels from
            all channels.
          schema:
            type: string
            enum:
              - all
              - email
              - chat
              - voice
              - phone
              - letter
              - internal
        - name: id
          in: query
          required: false
          description: Filter by a specific subchannel ID
          schema:
            type: integer
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Success'
                  - type: object
                    properties:
                      subchannels:
                        type: array
                        items:
                          $ref: '#/components/schemas/Subchannel'
        '403':
          description: Unauthorized
        '500':
          description: Internal error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Success:
      type: object
      description: Data format of Enneo success messages
      properties:
        success:
          type: boolean
          example: true
          description: Operation was successful
    Subchannel:
      type: object
      description: Subchannel object
      properties:
        id:
          type: integer
          example: 1
        channel:
          $ref: '#/components/schemas/Channel'
        name:
          type: string
          example: Support
        isDefault:
          type: boolean
          description: >-
            Whether this subchannel is the default for its channel. Only one
            subchannel per channel can be default.
          default: false
          example: false
        interface:
          type: string
          description: >-
            The underlying data source of this subchannel.


            Currently only 'internal' is supported, meaning the subchannel is
            managed directly by Enneo.
          enum:
            - internal
          example: internal
        enabled:
          type: boolean
          default: true
          example: true
        data:
          type: object
          nullable: true
          additionalProperties: true
          description: >-
            Channel-specific properties of this subchannel, e.g. IMAP Username
            and password for emails
    Error:
      type: object
      description: Data format of Enneo error messages
      properties:
        error:
          type: string
          example: Contract 121 could not be processed
          description: Readable error message that should be shown to the user
        details:
          type: string
          example: >-
            Uncatched null point exception in testFunction() in
            /app/src/file:212
          description: Not easily readable error message that is for the developer
        txId:
          type: string
          example: c916167c94
          description: >-
            Internal transaction id. Useful for debugging. Corresponds to the
            OpenTelemetry trace ID.
    Channel:
      type: string
      description: Channel of ticket
      enum:
        - email
        - portal
        - phone
        - letter
        - system
        - chat
        - walkIn
      example: email
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT-based authentication
      x-scopes:
        api: Full access to the API
    cookieAuth:
      type: apiKey
      in: cookie
      name: connect.sid
      description: Cookie-based authentication
      x-scopes:
        api: Full access to the API

````