> ## 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.

# Add a new Subchannel



## OpenAPI

````yaml https://dev.enneo.dev/api/mind/docs/open-api post /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:
    post:
      tags:
        - Settings
      summary: Add a new Subchannel
      operationId: createSubchannel
      requestBody:
        description: >-
          The new Subchannel that should be created. The ID does not need to be
          included in the payload, as it will be generated automatically.
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Subchannel'
      responses:
        '200':
          description: Subchannel added successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Indicates if the operation was successful
                    example: true
                  id:
                    type: integer
                    description: The ID of the added Subchannel
                    example: 12345
        '403':
          description: Unauthorized
        '500':
          description: Internal error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    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

````