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

# Post a comment on a DIR

> Post a customer comment on a DIR (for example, to respond to reviewer notes). Send only `content` (1–5000 chars) and an optional `parent_comment_id`; the server sets the comment type, visibility, and author automatically. The enterprise is resolved server-side from the DIR id.



## OpenAPI

````yaml https://telnyx-openapi-ng.s3.us-east-1.amazonaws.com/branded-calling/dirs.yml post /dir/{dir_id}/comments
openapi: 3.1.0
info:
  title: Telnyx Branded Calling Display Identity Records API
  version: 2.0.0
  description: >-
    Create and manage Display Identity Records (DIRs) — your branded caller
    identity — and submit them for vetting.
  contact:
    email: support@telnyx.com
servers:
  - url: https://api.telnyx.com/v2
security:
  - bearerAuth: []
paths:
  /dir/{dir_id}/comments:
    post:
      tags:
        - Comments
      summary: Post a comment on a DIR
      description: >-
        Post a customer comment on a DIR (for example, to respond to reviewer
        notes). Send only `content` (1–5000 chars) and an optional
        `parent_comment_id`; the server sets the comment type, visibility, and
        author automatically. The enterprise is resolved server-side from the
        DIR id.
      operationId: createCommentSimple
      parameters:
        - $ref: '#/components/parameters/DirId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DirCommentCreateRequest'
            example:
              content: >-
                Re-uploaded the certificate. New document_id:
                89450109-ee35-411c-b5bb-14f1d806fca2.
      responses:
        '201':
          description: Comment created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommentWrapped'
        default:
          $ref: '#/components/responses/branded-calling_GenericErrorResponse'
        4XX:
          $ref: '#/components/responses/branded-calling_GenericErrorResponse'
      x-codeSamples:
        - lang: JavaScript
          source: >-
            import Telnyx from 'telnyx';


            const client = new Telnyx({
              apiKey: process.env['TELNYX_API_KEY'], // This is the default and can be omitted
            });


            const comment = await
            client.dir.comments.create('16635d38-75a6-4481-82e8-69af60e05011', {
              content: 'Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2.',
            });


            console.log(comment.data);
        - lang: Python
          source: |-
            import os
            from telnyx import Telnyx

            client = Telnyx(
                api_key=os.environ.get("TELNYX_API_KEY"),  # This is the default and can be omitted
            )
            comment = client.dir.comments.create(
                dir_id="16635d38-75a6-4481-82e8-69af60e05011",
                content="Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2.",
            )
            print(comment.data)
        - lang: Go
          source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\n\t\"github.com/team-telnyx/telnyx-go\"\n\t\"github.com/team-telnyx/telnyx-go/option\"\n)\n\nfunc main() {\n\tclient := telnyx.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tcomment, err := client.Dir.Comments.New(\n\t\tcontext.TODO(),\n\t\t\"16635d38-75a6-4481-82e8-69af60e05011\",\n\t\ttelnyx.DirCommentNewParams{\n\t\t\tContent: \"Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2.\",\n\t\t},\n\t)\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", comment.Data)\n}\n"
        - lang: Java
          source: |-
            package com.telnyx.sdk.example;

            import com.telnyx.sdk.client.TelnyxClient;
            import com.telnyx.sdk.client.okhttp.TelnyxOkHttpClient;
            import com.telnyx.sdk.models.dir.comments.CommentCreateParams;
            import com.telnyx.sdk.models.dir.comments.CommentCreateResponse;

            public final class Main {
                private Main() {}

                public static void main(String[] args) {
                    TelnyxClient client = TelnyxOkHttpClient.fromEnv();

                    CommentCreateParams params = CommentCreateParams.builder()
                        .dirId("16635d38-75a6-4481-82e8-69af60e05011")
                        .content("Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2.")
                        .build();
                    CommentCreateResponse comment = client.dir().comments().create(params);
                }
            }
        - lang: Ruby
          source: |-
            require "telnyx"

            telnyx = Telnyx::Client.new(api_key: "My API Key")

            comment = telnyx.dir.comments.create(
              "16635d38-75a6-4481-82e8-69af60e05011",
              content: "Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2."
            )

            puts(comment)
        - lang: PHP
          source: >-
            <?php


            require_once dirname(__DIR__) . '/vendor/autoload.php';


            use Telnyx\Client;

            use Telnyx\Core\Exceptions\APIException;


            $client = new Client(apiKey: getenv('TELNYX_API_KEY') ?: 'My API
            Key');


            try {
              $comment = $client->dir->comments->create(
                '16635d38-75a6-4481-82e8-69af60e05011',
                content: 'Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2.',
                parentCommentID: '182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e',
              );

              var_dump($comment);
            } catch (APIException $e) {
              echo $e->getMessage();
            }
        - lang: CLI
          source: |-
            telnyx dir:comments create \
              --api-key 'My API Key' \
              --dir-id 16635d38-75a6-4481-82e8-69af60e05011 \
              --content 'Re-uploaded the certificate. New document_id: 89450109-ee35-411c-b5bb-14f1d806fca2.'
components:
  parameters:
    DirId:
      name: dir_id
      in: path
      description: The DIR id. Lowercase UUID.
      required: true
      schema:
        type: string
        format: uuid
        example: 16635d38-75a6-4481-82e8-69af60e05011
  schemas:
    DirCommentCreateRequest:
      type: object
      required:
        - content
      description: >-
        Customer-facing comment body. The server forces
        `comment_type=customer_inquiry`, `visibility=customer`, and
        `author_role=customer`; clients cannot override these. `author_name` is
        dropped to prevent admin-impersonation.
      properties:
        content:
          type: string
          minLength: 1
          maxLength: 5000
          description: Comment body. 1–5000 characters.
          example: Re-uploaded the logo as a 256×256 BMP. Please re-review.
        parent_comment_id:
          type: string
          format: uuid
          description: Optional parent comment id to thread this reply under.
    CommentWrapped:
      type: object
      required:
        - data
      properties:
        data:
          $ref: '#/components/schemas/DirComment'
    DirComment:
      type: object
      properties:
        id:
          type: string
          format: uuid
          example: 30bbd13c-1f3a-47c0-8fa6-718835917b2f
          readOnly: true
        entity_type:
          type: string
          enum:
            - dir
          description: Resource the comment is attached to. Always `dir` on this endpoint.
          example: dir
          readOnly: true
        content:
          type: string
          example: Please re-upload a clearer scan of the certificate.
        visibility:
          type: string
          enum:
            - customer
          description: >-
            Always `customer` on this endpoint - internal-only comments are
            filtered out.
          example: customer
          readOnly: true
        author_role:
          type: string
          enum:
            - customer
            - admin
          description: Who wrote the comment. `admin` covers the Telnyx vetting team.
          example: customer
          readOnly: true
        author_name:
          type: string
          nullable: true
          description: Display name of the author. May be `null`.
          example: null
          readOnly: true
        comment_type:
          $ref: '#/components/schemas/CommentType'
        created_at:
          type: string
          format: date-time
          example: '2026-04-27T00:42:44.305835Z'
          readOnly: true
    branded-calling_Errors:
      type: object
      required:
        - errors
      properties:
        errors:
          type: array
          items:
            $ref: '#/components/schemas/branded-calling_Error'
          description: List of one or more error entries. Order is not significant.
      description: >-
        Canonical Telnyx error envelope. Returned on every 4xx and 5xx response
        from this service. `errors` is non-empty; multiple entries indicate
        multiple distinct problems with the same request (e.g. one entry per
        invalid phone number on a bulk operation).
    CommentType:
      type: string
      enum:
        - vetting_comment
        - rejection_reason
        - internal_note
        - notification
        - status_update
        - customer_inquiry
        - admin_response
      description: >-
        Comment categorisation. Customers post `customer_inquiry`. The Telnyx
        team posts `vetting_comment`, `rejection_reason`, `notification`,
        `status_update`, or `admin_response`. `internal_note` is filtered out of
        customer-visible responses.
    branded-calling_Error:
      type: object
      required:
        - code
        - title
        - detail
        - meta
      properties:
        code:
          type: string
          example: '10005'
          description: >-
            Stable numeric Telnyx error catalog id. See `meta.url` for the full
            catalog entry.
        title:
          type: string
          example: Invalid parameters
          description: >-
            Short human-readable category, e.g. `Bad Request`, `Duplicate
            resource`, `Not Found`, `Forbidden`. Treat as advisory only - the
            stable identifier is `code`.
        detail:
          type: string
          example: field required
          description: >-
            Context-specific message describing what went wrong on this
            particular request. May embed offending values; do not rely on it
            for programmatic matching - branch on `code`.
        meta:
          type: object
          required:
            - url
          properties:
            url:
              type: string
              format: uri
              example: https://developers.telnyx.com/docs/overview/errors/10005
            pending_check_ids:
              type: array
              items:
                type: string
                format: uuid
              description: >-
                Set on `422 vetting_checks_incomplete` responses from
                `/admin/dir/{id}/approve` and
                `/admin/phone-number-batches/approve`. Lists the still-pending
                vetting check ids.
            pending_check_codes:
              type: array
              items:
                type: string
              description: >-
                Codes of the pending vetting checks (e.g.
                `loa_signature_valid`).
            pending_check_labels:
              type: array
              items:
                type: string
              description: Human-readable labels of the pending vetting checks.
          description: >-
            Carries `url` linking to the Telnyx error catalog entry for this
            `code`. Useful for forwarding the user to documentation.
        source:
          type: object
          description: Optional pointer at the offending field of the request.
          properties:
            pointer:
              type: string
              example: /body/legal_name
            parameter:
              type: string
              example: page[size]
      description: >-
        A single entry in the canonical Telnyx error envelope. `code` is the
        stable Telnyx error catalog id; the human-readable explanation lives at
        `meta.url`. `detail` is a context-specific message; `source.pointer`
        (when present) names the offending field of the request.
  responses:
    branded-calling_GenericErrorResponse:
      description: >-
        An error occurred. The response carries the standard Telnyx error
        envelope.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/branded-calling_Errors'
          examples:
            validation_error:
              summary: 422 - request body failed validation
              value:
                errors:
                  - code: '10005'
                    title: Invalid parameters
                    detail: field required
                    meta:
                      url: https://developers.telnyx.com/docs/overview/errors/10005
                    source:
                      pointer: /body/legal_name
            bad_request:
              summary: 400 - request rejected by a state guard
              description: >-
                Returned when the request itself is well-formed but the resource
                is in a state that disallows this action (e.g. updating a DIR
                while it is being vetted, or deleting an enterprise that still
                has DIRs in vetting).
              value:
                errors:
                  - code: '10015'
                    title: Bad Request
                    detail: Cannot update DIR in 'verified' status
                    meta:
                      url: https://developers.telnyx.com/docs/overview/errors/10015
            not_found:
              summary: 404 - resource does not exist or is not yours
              value:
                errors:
                  - code: '10009'
                    title: Resource not found
                    detail: Enterprise not found.
                    meta:
                      url: https://developers.telnyx.com/docs/overview/errors/10009
            conflict:
              summary: 409 - request conflicts with current resource state
              value:
                errors:
                  - code: '10021'
                    title: Resource in use
                    detail: >-
                      DIR has 1 active infringement claim(s). Resolve the claim
                      before making this change.
                    meta:
                      url: https://developers.telnyx.com/docs/overview/errors/10021
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http

````