🔑

Token Recovery

Lost your API token? Don't worry — it happens! API tokens are only shown once for security reasons, but getting a new one is quick and easy.

Why can't I see my existing token?
For security, we store tokens as one-way hashes. This means even we can't see your original token. If someone gained access to our database, they couldn't steal your token. The trade-off is you need to save it when it's first shown.

Recovery Steps

1

Delete Your Old Token

Go to your API token management page and delete any existing tokens.

Log in first, then go to Profile → API Tokens

2

Create a New Token

Generate a fresh API token. Copy it immediately! You won't be able to see it again after leaving the page.

💡 Tip: Keep the token page open until you've successfully updated your environment variable and tested it.

3

Update Your Environment Variable

Replace your old token with the new one in your shell profile.

Windows macOS Linux

4

Test Your New Token

Verify the new token works before closing the token page.

curl -H "X-API-Token: $VIBE9_API_TOKEN" https://vibe9.net/api/test-token.php

You should see a success message with your username.

Let Your AI Help

Copy this prompt to your AI coding assistant and it will guide you through the recovery process:

I need to recover my Vibe9 API token. The old one is lost/not working.

Please help me:
1. I'll go to https://vibe9.net/profile/api-token.php to delete my old token and create a new one
2. Once I have the new token, help me update my environment variable
3. Test the new token to make sure it works

I'm using [Windows/macOS/Linux] and [Claude Code/Cursor/Windsurf/other].

Recovery guide: https://vibe9.net/skill/setup/token-recovery/

💻 Multiple Machines?
If you use the same token on multiple computers, you'll need to update the environment variable on each one. Alternatively, you can create separate tokens (up to 5) for each machine.

Preventing Future Token Loss

✓ Save new tokens to a password manager immediately
✓ Keep the token page open until you've tested successfully
✓ Use separate tokens for each machine (easier to revoke individually)
✓ Consider adding a comment in your shell profile noting what the token is for