---
title: "Revoke a share"
method: DELETE
path: "/internal/api/clients/{client_id}/dms/shares/{share_id}"
tags: ["CLIENT", "Client Document Management", "DMS Shares"]
---

# Revoke a share

`DELETE /internal/api/clients/{client_id}/dms/shares/{share_id}`

## Request

- Base URL: `https://api.signalshq.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.signalshq.io/internal/api/clients/{client_id}/dms/shares/{share_id}`
- Auth: OAuth 2
  - Password
  - Token URL: `/auth/login`

Deactivate a share so the client can no longer access the resource. Returns a warnings array when the document is still reachable via an ancestor folder share (the direct share has been removed but the CPA must also move or unshare the folder to fully revoke access).

## Path parameters

- `share_id` string, uuid, required
- `client_id` string, uuid, required: Client ID

## Response `200`

Successful Response

- RevokeShareResponse: Response returned after revoking a share. warnings is non-empty when the document is still accessible to the client through a folder share (e.g. the document lives inside a shared ancestor folder). The CPA must also move the document out of the shared folder, or unshare the folder, to fully revoke access.
  - `share_id` string, uuid, required: UUID of the share that was revoked
  - `warnings` string[]: Non-empty when the client still has access to the document via an ancestor folder share after this direct share was revoked.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/signalshq/apis/signals-api.md) - [All operations](https://skmtc.dev/signalshq/apis/signals-api/llms.txt) - [OpenAPI document](https://skmtc.dev/signalshq/apis/signals-api/revisions/2c22af3b5576?raw)