> ## 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. # Update a DIR to resolve an infringement concern > Push a fix for a DIR that is `suspended` with an open infringement claim back into vetting. `POST /dir/{dir_id}/submit` is blocked while a claim is open, so this is the customer-callable path to update the DIR's content and re-certify before Telnyx adjudicates the claim. All four certification booleans must be `true`. Optional content fields (`display_name`, `logo_url`, `call_reasons`, `documents`) update the DIR; documents are append-only. ## OpenAPI ````yaml /openapi/source/external/branded-calling/branded-calling.json put /dir/{dir_id}/infringement_update openapi: 3.0.0 info: x-latency-category: responsive version: 2.0.0 title: Telnyx Branded Calling API description: >- The Telnyx Branded Calling API lets you register your business identity as Display Identity Records (DIRs) and associate phone numbers so your verified caller identity is shown on outbound calls. Flow: create an enterprise → activate Branded Calling → create a DIR → submit it for vetting → after approval, attach phone numbers and submit them in a batch for vetting. Several actions are billable (Branded Calling activation and phone-number registration). See https://telnyx.com/pricing/numbers for current pricing. contact: email: support@telnyx.com servers: - url: https://api.telnyx.com/v2 description: Telnyx API v2 (production) security: - bearerAuth: [] tags: - name: Enterprises description: Manage the legal-entity record that owns your DIRs and phone numbers. - name: Display Identity Records description: >- A Display Identity Record (DIR) is the verified calling identity (display name, logo, call reasons) shown to recipients on outbound calls. - name: DIR References description: >- Submit and manage the two business references and one financial reference that vouch for a DIR. References are contacted to confirm the business identity during vetting. - name: Email Verification description: >- Verify ownership of a DIR's authorizer email. A short code is emailed and confirmed; the email must be verified before references can be submitted. - name: Phone Numbers description: >- Associate phone numbers with a verified DIR so calls from those numbers carry the DIR's display identity. - name: Phone Number Batches description: >- Phone numbers are submitted to Telnyx for vetting in batches. Batches group all numbers added in a single request under the same Letter of Authorization. - name: Comments description: >- Read messages from the Telnyx vetting team and reply with clarifying information. - name: Infringement Claims description: >- Trademark or impersonation claims filed against your DIR. Customers may contest a claim with supporting evidence. - name: Reference Data description: >- Static reference values the API accepts: call reasons, document types, rejection types. - name: Terms of Service description: >- Accept and review the Branded Calling and Phone Number Reputation terms of service. paths: /dir/{dir_id}/infringement_update: put: tags: - Infringement Claims summary: Update a DIR to resolve an infringement concern description: >- Push a fix for a DIR that is `suspended` with an open infringement claim back into vetting. `POST /dir/{dir_id}/submit` is blocked while a claim is open, so this is the customer-callable path to update the DIR's content and re-certify before Telnyx adjudicates the claim. All four certification booleans must be `true`. Optional content fields (`display_name`, `logo_url`, `call_reasons`, `documents`) update the DIR; documents are append-only. operationId: updateDirInfringement parameters: - $ref: '#/components/parameters/DirId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DirInfringementUpdateRequest' example: certify_no_infringement: true certify_brand_is_accurate: true certify_no_shaft_content: true certify_ip_ownership: true infringement_resolution_notes: >- Updated the display name to remove the disputed mark and re-uploaded the authorization. responses: '200': description: DIR updated and re-submitted for vetting. content: application/json: schema: $ref: '#/components/schemas/DirWrapped' '400': $ref: '#/components/responses/GenericErrorResponse' '401': $ref: '#/components/responses/GenericErrorResponse' '404': $ref: '#/components/responses/GenericErrorResponse' '409': $ref: '#/components/responses/GenericErrorResponse' '422': $ref: '#/components/responses/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 response = await client.dir.updateInfringement('16635d38-75a6-4481-82e8-69af60e05011', { certify_brand_is_accurate: true, certify_ip_ownership: true, certify_no_infringement: true, certify_no_shaft_content: true, infringement_resolution_notes: 'Updated the display name to remove the disputed mark and re-uploaded the authorization.', }); console.log(response.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 ) response = client.dir.update_infringement( dir_id="16635d38-75a6-4481-82e8-69af60e05011", certify_brand_is_accurate=True, certify_ip_ownership=True, certify_no_infringement=True, certify_no_shaft_content=True, infringement_resolution_notes="Updated the display name to remove the disputed mark and re-uploaded the authorization.", ) print(response.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\tresponse, err := client.Dir.UpdateInfringement(\n\t\tcontext.TODO(),\n\t\t\"16635d38-75a6-4481-82e8-69af60e05011\",\n\t\ttelnyx.DirUpdateInfringementParams{\n\t\t\tCertifyBrandIsAccurate: true,\n\t\t\tCertifyIPOwnership: true,\n\t\t\tCertifyNoInfringement: true,\n\t\t\tCertifyNoShaftContent: true,\n\t\t\tInfringementResolutionNotes: \"Updated the display name to remove the disputed mark and re-uploaded the authorization.\",\n\t\t},\n\t)\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", response.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.DirUpdateInfringementParams; import com.telnyx.sdk.models.dir.DirUpdateInfringementResponse; public final class Main { private Main() {} public static void main(String[] args) { TelnyxClient client = TelnyxOkHttpClient.fromEnv(); DirUpdateInfringementParams params = DirUpdateInfringementParams.builder() .dirId("16635d38-75a6-4481-82e8-69af60e05011") .certifyBrandIsAccurate(DirUpdateInfringementParams.CertifyBrandIsAccurate.TRUE) .certifyIpOwnership(DirUpdateInfringementParams.CertifyIpOwnership.TRUE) .certifyNoInfringement(DirUpdateInfringementParams.CertifyNoInfringement.TRUE) .certifyNoShaftContent(DirUpdateInfringementParams.CertifyNoShaftContent.TRUE) .infringementResolutionNotes("Updated the display name to remove the disputed mark and re-uploaded the authorization.") .build(); DirUpdateInfringementResponse response = client.dir().updateInfringement(params); } } - lang: Ruby source: |- require "telnyx" telnyx = Telnyx::Client.new(api_key: "My API Key") response = telnyx.dir.update_infringement( "16635d38-75a6-4481-82e8-69af60e05011", certify_brand_is_accurate: true, certify_ip_ownership: true, certify_no_infringement: true, certify_no_shaft_content: true, infringement_resolution_notes: "Updated the display name to remove the disputed mark and re-uploaded the authorization." ) puts(response) - lang: PHP source: >- dir->updateInfringement( '16635d38-75a6-4481-82e8-69af60e05011', certifyBrandIsAccurate: true, certifyIPOwnership: true, certifyNoInfringement: true, certifyNoShaftContent: true, infringementResolutionNotes: 'Updated the display name to remove the disputed mark and re-uploaded the authorization.', callReasons: ['string'], displayName: 'x', documents: [ [ 'documentID' => '2a7e8337-e803-4057-a4ae-26c40eb0bc6c', 'documentType' => 'business_registration', 'description' => 'Certificate of incorporation.', ], ], logoURL: 'logo_url', ); var_dump($response); } catch (APIException $e) { echo $e->getMessage(); } - lang: CLI source: |- telnyx dir update-infringement \ --api-key 'My API Key' \ --dir-id 16635d38-75a6-4481-82e8-69af60e05011 \ --certify-brand-is-accurate true \ --certify-ip-ownership true \ --certify-no-infringement true \ --certify-no-shaft-content true \ --infringement-resolution-notes 'Updated the display name to remove the disputed mark and re-uploaded the authorization.' 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: DirInfringementUpdateRequest: type: object required: - certify_no_infringement - certify_brand_is_accurate - certify_no_shaft_content - certify_ip_ownership - infringement_resolution_notes properties: certify_no_infringement: type: boolean description: Must be `true`. enum: - true certify_brand_is_accurate: type: boolean description: Must be `true`. enum: - true certify_no_shaft_content: type: boolean description: Must be `true`. enum: - true certify_ip_ownership: type: boolean description: Must be `true`. enum: - true infringement_resolution_notes: type: string minLength: 10 maxLength: 500 description: Explanation of how the infringement concern was addressed. display_name: type: string nullable: true minLength: 1 maxLength: 35 logo_url: type: string nullable: true maxLength: 128 description: >- Publicly accessible HTTPS URL (max 128 chars) to a 256x256 BMP logo (max 1 MB). call_reasons: type: array items: type: string nullable: true minItems: 1 maxItems: 10 documents: type: array items: $ref: '#/components/schemas/Document' nullable: true maxItems: 20 description: >- Append-only supporting documents to attach while resolving the claim (e.g. authorization or licensing proof). DirWrapped: type: object required: - data properties: data: $ref: '#/components/schemas/Dir' Document: type: object required: - document_id - document_type properties: document_id: type: string format: uuid description: >- Id returned by the Telnyx Documents API after you upload the file (upload via `POST /v2/documents`; see https://developers.telnyx.com/api/documents). example: 2a7e8337-e803-4057-a4ae-26c40eb0bc6c document_type: type: string enum: - letter_of_authorization - business_registration - articles_of_incorporation - tax_document - ein_letter - trademark_registration - website_ownership - business_license - professional_license - government_id - utility_bill - bank_statement - other example: business_registration description: >- Type of supporting document. Pick the closest match to what the file actually contains; `other` triggers manual vetting and may slow approval. The matching short_name reference list is at `GET /v2/dir/document_types`. description: type: string maxLength: 255 example: Certificate of incorporation. Dir: type: object properties: id: type: string format: uuid example: 16635d38-75a6-4481-82e8-69af60e05011 readOnly: true enterprise_id: type: string format: uuid example: 4a6192a4-573d-446d-b3ce-aff9117272a6 display_name: type: string example: Acme Plumbing reselling: type: boolean example: false certify_brand_is_accurate: type: boolean example: true certify_no_shaft_content: type: boolean example: true certify_ip_ownership: type: boolean example: true authorizer_name: type: string nullable: true example: Sam Owner authorizer_email: type: string format: email nullable: true example: sam@acmeplumbing.example.com logo_url: type: string format: uri nullable: true example: https://acmeplumbing.example.com/logo-256.bmp call_reasons: type: array items: $ref: '#/components/schemas/CallReason' documents: type: array items: $ref: '#/components/schemas/Document' nullable: true status: $ref: '#/components/schemas/DirStatus' rejection_reasons: type: array items: $ref: '#/components/schemas/RejectionReason' nullable: true description: >- Populated when `status` is `rejected`; cleared on `/submit` or successful approval. rejected_at: type: string format: date-time nullable: true readOnly: true created_at: type: string format: date-time example: '2026-04-26T18:06:51.940749Z' readOnly: true updated_at: type: string format: date-time example: '2026-04-26T18:09:24.785211Z' readOnly: true submitted_at: type: string format: date-time nullable: true example: '2026-04-26T18:07:03.716411Z' readOnly: true verified_at: type: string format: date-time nullable: true example: '2026-04-26T18:07:29.537926Z' readOnly: true expiring_at: type: string format: date-time nullable: true example: '2027-04-26T18:07:29.537981Z' readOnly: true Errors: type: object required: - errors properties: errors: type: array items: $ref: '#/components/schemas/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). CallReason: type: object properties: reason: type: string maxLength: 64 example: Appointment reminders created_at: type: string format: date-time example: '2026-04-26T18:06:51.940749Z' readOnly: true DirStatus: type: string enum: - draft - submitted - in_review - verified - rejected - unsuccessful - suspended - expired - infringement_claimed - permanently_rejected description: >- DIR lifecycle status. - `draft` - newly created; editable; not yet submitted. - `submitted` / `in_review` - Telnyx is reviewing. - `verified` - approved; phone numbers may be attached. - `rejected` - Telnyx rejected this submission; `rejection_reasons` is populated; customer can edit and resubmit. - `unsuccessful` - system-side error during processing; customer can edit and resubmit. - `suspended` - temporarily disabled (e.g. by an active infringement claim). - `expired` - verification expired; customer must resubmit. - `infringement_claimed` - a trademark/impersonation claim is open against this DIR. - `permanently_rejected` - terminal; cannot be resubmitted. RejectionReason: type: object properties: code: type: string example: documentation_incomplete title: type: string example: Documentation incomplete detail: type: string example: Provided documents do not establish business identity. message: type: string nullable: true description: >- Customer-visible free-text comment from the Telnyx vetting team. Only the first entry of `rejection_reasons` carries this; the rest are `null`. example: Please re-upload a clearer scan of the certificate. 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: GenericErrorResponse: description: >- An error occurred. The response carries the standard Telnyx error envelope. content: application/json: schema: $ref: '#/components/schemas/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: type: http scheme: bearer description: >- Telnyx API key. Generate one at https://portal.telnyx.com/#/app/api-keys. ````