> 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/list-acls.md).

# List ACLs

Lists all ACL rules configured on a virtual cluster.

Requires admin or read-only permissions.

## Request

{% code overflow="wrap" %}

```bash
curl https://api.warpstream.com/api/v1/virtual_clusters/acls/list \
-H 'warpstream-api-key: XXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{"virtual_cluster_id": "vci_1d4930d7_8e6d_4ad9_b27a_654ed4aaa3ee"}'
```

{% endcode %}

## Response

```json
{
  "acls": [
    {
      "resource_type": "TOPIC",
      "resource_name": "orders",
      "pattern_type": "LITERAL",
      "principal": "User:alice",
      "host": "*",
      "operation": "READ",
      "permission_type": "ALLOW",
      "created_at": "2026-10-01T11:01:04.789Z"
    },
    {
      "resource_type": "TOPIC",
      "resource_name": "events",
      "pattern_type": "PREFIXED",
      "principal": "User:bob",
      "host": "*",
      "operation": "WRITE",
      "permission_type": "ALLOW"
    }
  ]
}
```

`created_at` is when the ACL was created, as an RFC 3339 UTC timestamp. Creating an ACL that already exists keeps its original `created_at`. Omitted for ACLs created before October 2026 when creation times started being recorded.

If no ACLs are configured, the response will contain an empty array:

```json
{
  "acls": []
}
```


---

# 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/list-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.