> 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/scripts-and-webhooks.md).

# Scripts, webhooks, and media routes

These are dashboard-session routes. They are not authenticated by a management bearer token.

| Method        | Route                                          | Purpose                                       |
| ------------- | ---------------------------------------------- | --------------------------------------------- |
| GET, POST     | /api/scripts                                   | List account scripts / publish original input |
| PATCH, DELETE | /api/scripts/{id}                              | Edit/link/move metadata / delete              |
| GET           | /api/scripts/{id}/content                      | Read stored protected payload                 |
| POST          | /api/scripts/{id}/rebuild                      | Rebuild with newly supplied original input    |
| POST          | /api/scripts/{id}/rotate                       | Rotate loader bootstrap/URL                   |
| GET           | /api/obfuscation/usage                         | Current publishing allowance usage            |
| GET, POST     | /api/projects/{id}/webhooks                    | List/create notification webhooks             |
| PATCH, DELETE | /api/projects/{id}/webhooks/{webhookId}        | Edit/delete webhook                           |
| POST          | /api/projects/{id}/webhooks/validate           | Validate a Discord webhook destination        |
| POST          | /api/projects/{id}/webhooks/{webhookId}/test   | Send a test notification                      |
| GET           | /api/projects/{id}/webhooks/{webhookId}/status | Delivery status                               |
| POST          | /api/projects/{id}/webhooks/{webhookId}/brand  | Apply/revert Discord branding                 |
| POST          | /api/avatars                                   | Upload an allowed avatar asset                |
| GET           | /api/avatar/{userId}                           | Serve/resolve an account avatar               |
| GET           | /api/avatar/file/{key...}                      | Serve an avatar object                        |

Publishing retains protected output, not original source. The filename "content" does not promise original input. Resource ownership/team checks apply to script operations; webhook secrets are masked in responses.

## Compatibility routes

| Method | Route                                    | Current use                                                 |
| ------ | ---------------------------------------- | ----------------------------------------------------------- |
| GET    | /api/projects/{id}/loadstring.lua        | Retired project loader URL; use /v1/loaders/{hash}.lua      |
| GET    | /api/projects/{id}/scripts/{alias}/raw   | Retired raw delivery                                        |
| GET    | /api/projects/{id}/scripts/{alias}       | Retired per-project script surface                          |
| GET    | /api/projects/{id}/scripts/{alias}/stats | Active dashboard stats; alias segment takes the script UUID |

The stats route remains active even though adjacent raw delivery routes are retired. It requires a project UUID and script UUID despite the legacy alias segment name. Use v2 loader stats for new backend integrations.


---

# 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/scripts-and-webhooks.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.