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

# LootLabs

1. Get the LootLabs credential used by its redirect/encryption integration.
2. Enter it in the project's LootLabs provider settings.
3. Add links owned by the same LootLabs account as the credential.
4. Add a package, enable the provider, save, and test the public flow.

Vampauth prepares a per-session redirect and sends the user back through `/api/integrations/lootlabs/callback`. The destination is prepared for that attempt; you don't copy a temporary callback token into a permanent public link.

If the credential is accepted but a run fails, check account ownership of the links and whether LootLabs is available. A saved credential is not proof that a complete checkpoint round-trip has passed.

Keep the original browser session through the return. Reusing someone else's destination, replaying an old callback, or opening it in another browser won't grant progress.