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

# Delete an Alert Channel

> Soft-deletes one channel owned by your workspace.



## OpenAPI

````yaml delete /v1/risk/channels/{channel_id}
openapi: 3.0.0
info:
  title: Range Risk API
  description: The Range Risk API for risk assessment of crypto addresses.
  version: 1.7.8
  contact: {}
servers:
  - url: https://api.range.org
    description: Range API Server
security:
  - Authorization: []
tags:
  - name: Risk
    description: Get risk information about a crypto address.
  - name: Risk v2
    description: >-
      Address risk assessment, workspace configuration, and signals catalogue
      (API v2).
  - name: Simulator
    description: Simulate a transaction on a network.
  - name: Alert Templates
    description: Browse alert rule templates available to the workspace.
  - name: Alert Rules
    description: Create and manage workspace alert rules.
  - name: Alert Events
    description: List and retrieve fired alert events.
  - name: Channels
    description: Configure alert delivery channels.
paths:
  /v1/risk/channels/{channel_id}:
    delete:
      tags:
        - Channels
      summary: Delete a channel
      description: >-
        Soft-deletes one channel owned by your workspace: it is disabled and
        hidden from list/get, but the row is retained (only `deleted_at` is
        stamped).
      operationId: deleteChannel
      parameters:
        - name: channel_id
          required: true
          in: path
          description: The channel id.
          schema:
            type: string
            example: 44444444-4444-4444-4444-444444444445
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteAlertChannelResponseDto'
components:
  schemas:
    DeleteAlertChannelResponseDto:
      type: object
      properties:
        acknowledged:
          type: boolean
          example: true
      required:
        - acknowledged
  securitySchemes:
    Authorization:
      scheme: bearer
      bearerFormat: API Key
      description: 'Use Authorization: Bearer <api-key>'
      type: http

````