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

# Delete a Counterparty Contact

> Delete one of your application's own compliance contacts for a counterparty VASP. The Travel Rule email rail stops writing to it at once.

Delete a Counterparty Contact API Prompt
Copy prompt to clipboard

<pre>
  \`Delete one of my application's own Travel Rule counterparty contacts.

  Endpoint:
  DELETE [https://verification.didit.me/v3/travel-rule/counterparty-contacts/\{contact\_uuid}/](https://verification.didit.me/v3/travel-rule/counterparty-contacts/\{contact_uuid}/)

  Authentication:
  Use the x-api-key header with my Didit API key.

  What happens:

  * 204 - the contact is deleted and the EMAIL rail stops writing to it.
  * 404 - no contact of my application has this id. Platform contacts (scope platform), another application's contacts and contacts already deleted answer 404 too.

  Full guide: /transaction-monitoring/travel-rule#contacts.\`
</pre>

Paste into


## OpenAPI

````yaml DELETE /v3/travel-rule/counterparty-contacts/{contact_uuid}/
openapi: 3.0.0
info:
  version: 3.0.0
  title: Didit Verification API
  description: Identity verification API. Authenticate with x-api-key header.
servers:
  - url: https://verification.didit.me
security: []
tags: []
paths:
  /v3/travel-rule/counterparty-contacts/{contact_uuid}/:
    delete:
      tags:
        - Travel Rule
      summary: Delete a counterparty contact
      description: >-
        Deletes one of your application's own contacts. The EMAIL rail stops
        writing to it at once. Platform contacts cannot be deleted.
      operationId: deleteTravelRuleCounterpartyContact
      parameters:
        - name: contact_uuid
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '204':
          description: Deleted.
        '404':
          description: >-
            No contact of your application has this id. A platform contact
            answers 404 too.
      security:
        - ApiKeyAuth: []
      x-codeSamples:
        - lang: curl
          label: curl
          source: >-
            curl -X DELETE
            https://verification.didit.me/v3/travel-rule/counterparty-contacts/{contact_uuid}/
            \
              -H 'x-api-key: YOUR_API_KEY'
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Your application's API key, from Developers -> API keys in the Business
        Console. The primary key has full access. A named key can be scoped:
        none, read or write per resource, limited to some workflows or to
        approved sessions, to a list of IP addresses, and to an expiry date. 401
        means the key is missing, wrong, revoked or expired; 403 means the key
        has no access to this resource or action, or the request came from an
        address outside its IP list; 404 on a session route means the session is
        outside the key's workflows or statuses. A key without media access
        receives image, video and PDF URLs as null, and a key without sessions
        write receives session links and tokens as null. See
        https://docs.didit.me/console/api-keys.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.