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

# Create Topic

> Creates a subscription topic with a default subscription state and visibility.



## OpenAPI

````yaml /openapi.json post /topics
openapi: 3.1.0
info:
  title: Dugble API
  description: >-
    Programmatic access to Dugble email, SMS, sending infrastructure, contacts,
    audiences, suppressions, and broadcasts. Authenticate with a team token sent
    as a Bearer token.
  version: 1.0.0
  contact:
    name: Dugble Support
    email: support@dugble.com
servers:
  - url: https://api.dugble.com
    description: Production
security:
  - BearerAuth: []
tags:
  - name: Email
    description: Send and manage transactional emails.
  - name: SMS
    description: Send and manage SMS messages.
  - name: Domains
    description: Manage and verify sending domains.
  - name: Templates
    description: Create, version, publish, preview, and test reusable email templates.
  - name: Sender IDs
    description: Manage SMS sender IDs.
  - name: Contacts
    description: Manage contacts and their audience memberships.
  - name: Contact Properties
    description: Manage typed custom property definitions used by contacts.
  - name: Topics
    description: Manage contact subscription topics.
  - name: Segments
    description: Manage audience segments.
  - name: Suppressions
    description: Manage suppressed email recipients.
  - name: Broadcasts
    description: Create, schedule, and analyze email broadcasts.
paths:
  /topics:
    post:
      tags:
        - Topics
      summary: Create Topic
      description: >-
        Creates a subscription topic with a default subscription state and
        visibility.
      operationId: createTopic
      parameters:
        - $ref: '#/components/parameters/IdempotencyKey'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TopicCreateRequest'
            example:
              name: Product updates
              default_subscription: opt_in
              visibility: private
      responses:
        '200':
          description: Topic created successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MutationEnvelope'
        default:
          $ref: '#/components/responses/Error'
components:
  parameters:
    IdempotencyKey:
      name: Idempotency-Key
      in: header
      required: false
      description: Optional idempotency key for mutation requests. Maximum 256 characters.
      schema:
        type: string
        maxLength: 256
  schemas:
    TopicCreateRequest:
      type: object
      required:
        - name
        - default_subscription
      properties:
        name:
          type: string
          maxLength: 50
        description:
          type: string
          maxLength: 200
        default_subscription:
          type: string
          enum:
            - opt_in
            - opt_out
        visibility:
          type: string
          enum:
            - public
            - private
          default: private
    MutationEnvelope:
      type: object
      required:
        - success
        - data
      properties:
        success:
          type: boolean
          enum:
            - true
        data:
          $ref: '#/components/schemas/MutationResponse'
    MutationResponse:
      type: object
      required:
        - object
        - id
      properties:
        object:
          type: string
        id:
          type: string
          format: uuid
    ErrorEnvelope:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          enum:
            - false
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              enum:
                - BAD_REQUEST
                - UNAUTHORIZED
                - FORBIDDEN
                - STEP_UP_REQUIRED
                - NOT_FOUND
                - CONFLICT
                - PAYMENT_REQUIRED
                - PAYLOAD_TOO_LARGE
                - UNPROCESSABLE_ENTITY
                - TOO_MANY_REQUESTS
                - INTERNAL_ERROR
                - SERVICE_UNAVAILABLE
            message:
              type: string
  responses:
    Error:
      description: >-
        The request failed. See the HTTP status and structured error code for
        the category.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorEnvelope'
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: Team token
      description: >-
        Pass a Dugble team token in the Authorization header as Bearer <token>.
        Team token secrets use the dgb_team_ prefix.

````