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

# Management API v2

Base URL: `https://vampauth.com/api/v2`.

Use this API from your backend to manage resources. It is separate from standalone validation and the game-client loader protocol.

## Create a token

Open Settings → Developer API. Name a token, select scopes and optional projects, choose its expiry, and copy it once. The complete value cannot be revealed later.

```bash
curl --fail-with-body "https://vampauth.com/api/v2/me" -H "Authorization: Bearer $VAMPAUTH_TOKEN"
```

The header is `Authorization: Bearer va_api_…`. Default expiry is 90 days. Dated expiry must be more than five minutes and no more than 365 days away. Explicit lifetime tokens stay active until revoked. At most ten active tokens are allowed.

Token issuance/revocation use a logged-in browser session under `/api/settings/api-tokens`. A bearer token cannot issue another token. Replace a token by creating a new one, updating your integration, then revoking the old one. Already-admitted requests may finish after revocation.

## IDs

V2 resource paths use database UUIDs. A project's `id` is its UUID; `public_id` is the separate consumer-flow ID. Key actions use the key UUID, not its plaintext value. Use read-only POST lookup to find a key by its value.

## Response format

```json
{
  "data": [],
  "pagination": { "limit": 50, "has_more": false, "next_cursor": null },
  "meta": { "request_id": "req_example" }
}
```

Single-resource responses omit pagination. Errors use `error: {code, message, details?}` with `meta.request_id`. `X-Request-Id` matches that metadata. Resource responses are no-store. Protected payload reads return text/plain on success and the usual JSON error envelope on failure.

## Pagination

Growing collections default to 50 rows, maximum 200, newest first by created time and ID. Pass the opaque `next_cursor` unchanged with the same filters/grants/resource. Start over when changing filters. Pages aren't an immutable snapshot; counts aren't implicit. The fixed provider catalogue isn't paginated.

## Permissions

Every request needs a valid token, the operation scope, an allowed project grant, and current account/team capability. Write scopes do not imply read scopes. Selected-project tokens cannot create projects or access detached loaders. Removing access also blocks retries.

## Machine-readable definitions

The website serves `GET /api/v2/openapi.json` and `GET /api/v2/postman.json` publicly. They contain no credentials. Their live content follows the deployed website version; this documentation follows the dev revision named on Welcome.

The endpoint guides below cover all 51 authenticated operations in the current contract, plus the public schema/collection routes.

## In this section

* [Scopes and permissions](/vampauth-docs/api-reference/management/scopes.md)
* [Retries, revisions, and limits](/vampauth-docs/api-reference/management/retries-and-limits.md)
* [Account and projects](/vampauth-docs/api-reference/management/projects.md)
* [Keys](/vampauth-docs/api-reference/management/keys.md)
* [Groups and default payload](/vampauth-docs/api-reference/management/groups.md)
* [Loaders and publishing](/vampauth-docs/api-reference/management/loaders.md)
* [Providers](/vampauth-docs/api-reference/management/providers.md)
* [Hardware bans](/vampauth-docs/api-reference/management/hardware-bans.md)
* [Collaborators](/vampauth-docs/api-reference/management/collaborators.md)
* [Analytics and presence](/vampauth-docs/api-reference/management/analytics.md)


---

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