> For the complete documentation index, see [llms.txt](https://docs.warpstream.com/warpstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpstream.com/warpstream/reference/api-reference/acls/delete-acls.md).

# Delete ACLs

Deletes ACL rules that match the provided filters. Supports dry-run mode and bulk deletion.

Requires admin permissions.

## Request

{% code overflow="wrap" %}

```bash
curl https://api.warpstream.com/api/v1/virtual_clusters/acls/delete \
-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{
  "virtual_cluster_id": "vci_1d4930d7_8e6d_4ad9_b27a_654ed4aaa3ee",
  "acls": [
    {
      "resource_type": "TOPIC",
      "resource_name": "orders",
      "pattern_type": "LITERAL",
      "principal": "User:alice",
      "host": "*",
      "operation": "READ",
      "permission_type": "ALLOW"
    }
  ]
}'
```

{% endcode %}

Each filter in the `acls` array requires all fields: `resource_type`, `resource_name`, `pattern_type`, `principal`, `host`, `operation`, and `permission_type`.

## Response

The response contains the ACL rules that were deleted:

```json
{
  "acls": [
    {
      "resource_type": "TOPIC",
      "resource_name": "orders",
      "pattern_type": "LITERAL",
      "principal": "User:alice",
      "host": "*",
      "operation": "READ",
      "permission_type": "ALLOW"
    }
  ]
}
```

## Dry Run

Set `dry_run` to `true` to preview which ACLs would be deleted without actually removing them:

{% code overflow="wrap" %}

```bash
curl https://api.warpstream.com/api/v1/virtual_clusters/acls/delete \
-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{
  "virtual_cluster_id": "vci_1d4930d7_8e6d_4ad9_b27a_654ed4aaa3ee",
  "dry_run": true,
  "acls": [
    {
      "resource_type": "TOPIC",
      "resource_name": "orders",
      "pattern_type": "LITERAL",
      "principal": "User:alice",
      "host": "*",
      "operation": "READ",
      "permission_type": "ALLOW"
    }
  ]
}'
```

{% endcode %}

## Bulk Deletion

Set `bulk_deletion` to `true` to delete all ACLs matching broad criteria. In bulk mode, you filter only by `resource_type`, `pattern_type`, `operation`, and `permission_type`. The fields `resource_name`, `host`, and `principal` must be omitted (or empty).

{% code overflow="wrap" %}

```bash
curl https://api.warpstream.com/api/v1/virtual_clusters/acls/delete \
-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{
  "virtual_cluster_id": "vci_1d4930d7_8e6d_4ad9_b27a_654ed4aaa3ee",
  "bulk_deletion": true,
  "acls": [
    {
      "resource_type": "TOPIC",
      "pattern_type": "LITERAL",
      "operation": "READ",
      "permission_type": "ALLOW"
    }
  ]
}'
```

{% endcode %}

{% hint style="warning" %}
Bulk deletion can remove many ACLs at once. Use `dry_run` first to verify which ACLs will be affected.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.warpstream.com/warpstream/reference/api-reference/acls/delete-acls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.