---
title: "Contest an infringement claim"
method: POST
path: "/infringement_claims/{claim_id}/contest"
tags: ["Infringement Claims"]
---

# Contest an infringement claim

`POST /infringement_claims/{claim_id}/contest`

## Request

- Base URL: `https://api.telnyx.com/v2`
- URL: `https://api.telnyx.com/v2/infringement_claims/{claim_id}/contest`
- Auth: HTTP bearer

Submit a written response and supporting documents disputing the claim. The first call moves the claim from `pending` to `contested`; subsequent calls append supplementary evidence without changing status. The `documents[]` you attach are aggregated across rounds in the claim's `contest_documents` field.

Only `pending` and `contested` claims accept new evidence. A `resolved` claim returns `400`.

Failure modes:
- `400` - the claim is `resolved` (terminal); cannot be contested further.
- `404` - the claim does not exist or is not against a DIR you own.
- `422` - `contest_notes` is too short (< 10 chars), too long (> 2000 chars), `documents` is > 20 entries, or a `document_id` is duplicated within the same submission.

## Path parameters

- `claim_id` string, uuid, required

## Request body

- InfringementClaimContest
  - `contest_notes` string, required: Customer's response to the claim. 10–2000 characters.
  - `documents` Document[]: Up to 20 supporting documents per submission. `document_id` must be unique within this submission. Documents are aggregated into the claim's `contest_documents` across all submissions.
    - `document_id` string, uuid, required: Id returned by the Telnyx Documents API after you upload the file (upload via `POST /v2/documents`; see https://developers.telnyx.com/api/documents).
    - `document_type` 'letter_of_authorization' | 'business_registration' | 'articles_of_incorporation' | 'certificate_of_good_standing' | 'tax_document' | 'ein_letter' | 'trademark_registration' | 'website_ownership' | 'business_license' | 'professional_license' | 'government_id' | 'utility_bill' | 'bank_statement' | 'business_credit_report' | 'bank_reference_letter' | 'other', required: 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` string: An optional note describing this document, for example what it proves.

## Response `200`

Updated claim, status `contested`.

- InfringementClaimWrapped
  - `data` InfringementClaim, required
    - `id` string, uuid
    - `dir_id` string, uuid
    - `enterprise_id` string, uuid
    - `claim_type` 'trademark' | 'copyright': Category of infringement being claimed.
    - `claim_description` string
    - `claimant_name` string
    - `claimant_contact` string
    - `claim_date` string, date-time: When the claim was filed (set by the claimant's representative at file time).
    - `status` 'pending' | 'contested' | 'resolved': Lifecycle status. `pending` - newly filed; the DIR is auto-suspended. `contested` - you have submitted contest evidence; awaiting Telnyx review. `resolved` - final.
    - `resolution` 'upheld' | 'rejected' | 'modified', nullable: Set only when `status` is `resolved`.
    - `resolution_date` string, date-time, nullable
    - `resolution_notes` string, nullable
    - `contest_documents` Document[]: Aggregated across all customer contest submissions on this claim.
      - `document_id` string, uuid, required: Id returned by the Telnyx Documents API after you upload the file (upload via `POST /v2/documents`; see https://developers.telnyx.com/api/documents).
      - `document_type` 'letter_of_authorization' | 'business_registration' | 'articles_of_incorporation' | 'certificate_of_good_standing' | 'tax_document' | 'ein_letter' | 'trademark_registration' | 'website_ownership' | 'business_license' | 'professional_license' | 'government_id' | 'utility_bill' | 'bank_statement' | 'business_credit_report' | 'bank_reference_letter' | 'other', required: 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` string: An optional note describing this document, for example what it proves.
    - `contest_history` ContestSubmission[]: Per-round submission audit trail. Each entry records one `POST /infringement_claims/{id}/contest` call (notes, timestamp, document count). Aggregated documents live on `contest_documents`.
      - `notes` string
      - `submitted_at` string, date-time
      - `document_count` integer
    - `dir` InfringementClaimDirRef: Snapshot of the DIR the claim is filed against, embedded for convenience.
      - `id` string, uuid
      - `display_name` string
      - `enterprise_id` string, uuid
      - `status` 'draft' | 'submitted' | 'in_review' | 'verified' | 'rejected' | 'unsuccessful' | 'suspended' | 'expired' | 'infringement_claimed' | 'permanently_rejected' | 'delete_requested': 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. - `delete_requested` - you have requested deletion; the DIR still exists and Telnyx is completing the removal (de-registration and cleanup). A verified DIR keeps serving its branded identity, and keeps billing, until the removal finishes.
    - `created_at` string, date-time
    - `updated_at` string, date-time

## Other responses

- `default`: An error occurred. The response carries the standard Telnyx error envelope.
- `4XX`: An error occurred. The response carries the standard Telnyx error envelope.

## Changes

- **2026-10-19** `5beddb7ab8af`: 3 warning, 3 info
  - added the new `bank_reference_letter` enum value to the `data/contest_documents/items/document_type` response property for the response status `200`
  - added the new `business_credit_report` enum value to the `data/contest_documents/items/document_type` response property for the response status `200`
  - added the new `certificate_of_good_standing` enum value to the `data/contest_documents/items/document_type` response property for the response status `200`
  - added the new `bank_reference_letter` enum value to the request property `documents/items/document_type`
  - …2 more
- **2026-10-15** `a72569d69430`: 1 warning
  - added the new `delete_requested` enum value to the `data/dir/status` response property for the response status `200`
- **2026-06-05** `8a8c40f458c5`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/team-telnyx/apis/telnyx-api/changes/infringement_claims/:claim_id/contest/post.md)

---

[API](https://skmtc.dev/team-telnyx/apis/telnyx-api.md) - [All operations](https://skmtc.dev/team-telnyx/apis/telnyx-api/llms.txt) - [OpenAPI document](https://skmtc.dev/team-telnyx/apis/telnyx-api/revisions/a73101b68823?raw)