# Get the banning rule list (/en/api-reference/api-ref/rtc/get-ban-rule-list)

> For AI agents: see the complete documentation index at [llms.txt](/llms.txt).

Retrieves all banning rules.

- OpenAPI: /openapi/rtc/channel-management.en.yaml
- Operation ID: cma-get-ban-rule-list
- Method: GET
- Path: /dev/v1/kicking-rule

## Servers

- https://api.agora.io

## Parameters

- `appid` (query, required) - The App ID of the project. You can get it through one of the following methods:
- Copy from the [Agora Console](https://console.agora.io)
- Call the Get all projects API, and read the value of the
  `vendor_key` field in the response body.

## Request body

No request body.

## Responses

### 200

A `200` status code indicates success. The response body contains the result of the request.

- `status` (string) - The status of this request. `success` means the request succeeds.
No schema.
- `rules` (array) - The list of banning rules. Each object in the array represents one banning rule.
  - `rules.items` (object)
    - `rules.items.id` (number) - The rule ID. Required to update or delete the rule.
No schema.
    - `rules.items.appid` (string) - The App ID of the project.
No schema.
    - `rules.items.uid` (number) - The user ID.
No schema.
    - `rules.items.opid` (number) - The operation ID, which can be used to track operation records when troubleshooting.
No schema.
    - `rules.items.cname` (string) - The channel name.
No schema.
    - `rules.items.ip` (string) - The IP address of the user.
No schema.
    - `rules.items.ts` (string) - The UTC time when this rule expires.
No schema.
    - `rules.items.privileges` (array) - The banned user privileges. Possible values: `join_channel`, `publish_audio`, `publish_video`.
      - `rules.items.privileges.items` (string)
No schema.
    - `rules.items.createAt` (string) - The UTC time when this rule was created.
No schema.
    - `rules.items.updateAt` (string) - The UTC time when this rule was last updated.
No schema.
### default

The request failed. See the `message` field in the response body for the reason. Refer to Response status codes for details.

No schema.