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

# Providers

| Method and path                                      | Scope           |
| ---------------------------------------------------- | --------------- |
| GET /projects/{project\_id}/providers                | providers:read  |
| GET /projects/{project\_id}/providers/{provider\_id} | providers:read  |
| PUT /projects/{project\_id}/providers/{provider\_id} | providers:write |

All need manage\_checkpoints. Provider IDs: linkvertise, lootlabs, workink, linkunlocker. Reads return a project ETag. The catalogue is fixed/unpaginated and accepts no query fields.

## PUT fields

Requires project If-Match; optional Idempotency-Key. Maximum body: 64 KiB. Send a nonempty subset:

| Field             | Meaning                                                    |
| ----------------- | ---------------------------------------------------------- |
| enabled           | boolean                                                    |
| credential        | Up to 512 characters; omitted preserves; null/blank clears |
| links             | Up to 20 ordered link objects                              |
| packages          | Up to 10 package objects                                   |
| prepare\_callback | Prepare a callback anchor                                  |

Link: required HTTP(S) url up to 2048 characters, optional id (1–64 letters/digits/underscore/hyphen), optional positive integer workink\_link\_id. Package: checkpoints 1–50, expiry\_seconds 60–31536000, optional id and key\_group\_id (same-project UUID/null). IDs must be unique within each list. Supplied lists replace those configuration lists; preserve entries you want to keep.

```json
{
  "enabled": false,
  "links": [{ "id": "main", "url": "https://linkvertise.com/123/example" }],
  "packages": [{ "id": "hour", "checkpoints": 1, "expiry_seconds": 3600, "key_group_id": null }],
  "prepare_callback": true
}
```

This illustrative disabled configuration is not a completed connection. Supply a genuine credential privately, configure the provider return path, and enable after readiness passes.

## Response

id, project\_id, enabled, credential\_configured, callback\_url, links, packages, readiness. The secret isn't returned. readiness contains token/link/package/enabled booleans, missing items, and ready. PUT also returns callback\_rotated.

Used callback anchors may rotate on save. Existing retired anchors keep older links working; use the newly returned URL for a new Linkvertise target. See each provider's setup guide for its actual return flow.

## Next steps

* [Checkpoint providers](/vampauth-docs/integrations/checkpoint-providers.md)
* [Retries, revisions, and limits](/vampauth-docs/api-reference/management/retries-and-limits.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/providers.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.