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

# Browser and callback routes

The website has routes beyond the public v2 contract. They support authenticated dashboard requests, browser-owned checkpoint sessions, OAuth redirects, and provider callbacks. A v2 bearer token doesn't replace their cookies, origin checks, captcha tokens, or callback capabilities.

Use v2 for backend automation where an equivalent exists. The child route directories list the complete current surface so you can recognize requests in browser tools without treating every route as a public SDK.

Placeholder names in braces represent the matching path segment. Avatar catch-all keys can contain multiple segments. Unsupported methods may be exported solely to return a 405 response; that does not make them supported operations.

## In this section

* [Account and dashboard routes](/vampauth-docs/api-reference/browser-routes/account-and-dashboard.md)
* [Scripts, webhooks, and media routes](/vampauth-docs/api-reference/browser-routes/scripts-and-webhooks.md)
* [Flow and provider callback routes](/vampauth-docs/api-reference/browser-routes/flow-and-callbacks.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/browser-routes.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.