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

# Account and projects

All paths here are relative to `https://vampauth.com/api/v2`. JSON input rejects unknown fields.

| Method and path                | Scope           | Result                                                 |
| ------------------------------ | --------------- | ------------------------------------------------------ |
| GET /me                        | account:read    | Current identity and effective limits                  |
| GET /projects                  | projects:read   | Paginated current owned/member projects                |
| POST /projects                 | projects:write  | 201 with project and Location; unrestricted token only |
| GET /projects/{project\_id}    | projects:read   | Project data and project ETag                          |
| PATCH /projects/{project\_id}  | projects:write  | Updated project and ETag                               |
| DELETE /projects/{project\_id} | projects:delete | affected\_count and deleted-domain counts              |

List accepts `limit` and `cursor`. Project IDs are UUIDs.

## Create

Required `name`: trimmed, 1–50 characters, yielding a valid slug. Optional `settings`. Supply Idempotency-Key.

```json
{ "name": "My script", "settings": { "hwid_binding": true, "default_key_expiry_seconds": 86400 } }
```

## Edit

PATCH accepts `name` and/or `settings` with at least one actual field. It requires edit\_settings and If-Match. Optional idempotency key.

| Settings field                | Type/range                                                    |
| ----------------------------- | ------------------------------------------------------------- |
| hwid\_binding                 | boolean                                                       |
| default\_key\_expiry\_seconds | integer 60–31536000                                           |
| max\_keys\_per\_person        | integer 1–10                                                  |
| max\_hwid\_resets\_per\_key   | integer 1–20 or null                                          |
| stack\_cooldown\_seconds      | integer 0–86400                                               |
| loader\_lease\_enabled        | boolean                                                       |
| loader\_max\_concurrent       | integer 1–10                                                  |
| avatar\_url                   | HTTP(S) URL, max 2048 characters, or null; no URL credentials |
| keyless                       | off/always/scheduled object, or null                          |

Scheduled keyless settings contain kind weekends/custom, an IANA timezone, and custom windows with start\_at/end\_at. Custom windows are capped at 20 and the effective plan budget. Dedicated configuration domains—providers, groups, default payload, team, Discord claims and custom flow names—aren't arbitrary settings fields.

## Delete

Owner only, with If-Match. Empty body or {} is accepted. Deletes related keys/groups/rows and detaches account-owned loaders; stored loader outputs survive. A selected-project token cannot access those detached loaders afterward.

## Project response

Fields: id, public\_id, name, slug, settings, created\_at, updated\_at. Settings include normalized access defaults and default\_payload\_loader\_id. Private auth/provider credentials aren't part of this response.

## Account response

GET /me returns id, username, avatar\_url, limits, and current token metadata. Limits include max\_projects, max\_loaders, max\_loader\_bytes, obfuscation\_publishes\_per\_week, and max\_active\_api\_tokens (10). Token metadata includes id, name, scopes, project\_ids and expires\_at. It never returns the bearer value.


---

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