> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/api-reference/management/hardware-bans.md).

# Hardware bans

| Method and path                                    | Scope           |
| -------------------------------------------------- | --------------- |
| GET /projects/{project\_id}/hwid-bans              | hwid-bans:read  |
| POST /projects/{project\_id}/hwid-bans             | hwid-bans:write |
| DELETE /projects/{project\_id}/hwid-bans/{ban\_id} | hwid-bans:write |
| POST /projects/{project\_id}/hwid-bans/bulk        | hwid-bans:write |

All require manage\_hwid\_bans. List is paginated with limit/cursor and returns a project ETag. Body limit: 64 KiB. These mutations don't require If-Match.

Create body: hwid (trimmed 1–256 characters), optional reason (up to 200 characters/null). Requires Idempotency-Key; returns 201 with id, project\_id, hwid, reason, created\_at.

Delete accepts empty input/{} and optional Idempotency-Key; returns affected\_count. It removes the hardware ban, not the key ban.

Bulk requires Idempotency-Key and one of:

```json
{ "action": "ban", "hwids": ["DEVICE-HWID"], "reason": "Shared device" }
```

```json
{ "action": "unban", "ids": ["BAN-UUID"] }
```

Lists contain 1–100 distinct values. The action is atomic and returns affected\_count, with bans where applicable. A hardware ban applies across keys within the project, including FFA/binding-off admissions.


---

# 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://vampauth.gitbook.io/vampauth-docs/api-reference/management/hardware-bans.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.