---
title: "Revoke a WhatsApp connect link"
method: DELETE
path: "/api/v1/channels/connect-sessions/{id}"
tags: ["channels"]
---

# Revoke a WhatsApp connect link

`DELETE /api/v1/channels/connect-sessions/{id}`

## Request

- Base URL: `https://app.blueticked.com`
- URL: `https://app.blueticked.com/api/v1/channels/connect-sessions/{id}`
- Auth: HTTP bearer

Kill a link you have sent: wrong address, forwarded, or simply no longer wanted.

The customer holding a revoked link is told it was cancelled, not that it is invalid. That is a more useful answer, and the row is kept so you can still see the link existed.

A link that has ALREADY been used cannot be revoked: 409 resource_in_use. Revoking it would imply the connection it created had been undone, and it has not. Undoing that means disconnecting the channel instead.

Revoking an already-revoked link succeeds. You wanted it dead; it is dead.

An id from another workspace returns 404 rather than confirming it exists.

## Path parameters

- `id` string, required

## Response `200`

Success

- object
  - `id` string, uuid, required
  - `status` string, required
  - `request_id` string, required

## Other responses

- `400`: Validation failed
- `401`: Unauthorized: missing or invalid API key
- `402`: Insufficient wallet balance
- `403`: Forbidden: scope, plan limit, or suspension
- `404`: Not found
- `409`: Conflict (idempotency-key reuse or resource in use)
- `422`: Understood but refused: the request is well-formed, the action is not permitted for this resource
- `429`: Rate limited
- `500`: Internal error
- `502`: An upstream provider refused or failed the request
- `503`: Channel or send queue unavailable

---

[API](https://skmtc.dev/blueticked/apis/blueticked-api.md) · [All operations](https://skmtc.dev/blueticked/apis/blueticked-api/llms.txt) · [OpenAPI document](https://skmtc.dev/blueticked/apis/blueticked-api/revisions/07132284f4ff?raw)