BOT_TOKEN_INVALID

What triggered it

When you connect a Discord bot, we validate the token by calling Discord’s GET /users/@me endpoint with it. BOT_TOKEN_INVALID fires when one of the following happens:

• Format check failed — the token doesn’t look like a Discord bot token (missing dots, wrong length).
• Discord rejected it as expired — Discord revokes tokens automatically when they’re posted publicly (GitHub, screenshots, public Discord channels).
• Token is for a different bot type — you pasted a user token instead of a bot token.
• Missing intents — the application has gateway intents disabled. Discord rejects connections without required intents.
• Bot not in your team — the application’s owner isn’t you, so we can’t operate it.

Tokens leak. Always reset before pasting.

If your token has ever touched a screenshot, a Slack/Discord message, an email, or a git commit, assume it’s compromised. Discord scans GitHub for leaked tokens and revokes them within minutes. Reset before pasting into VibeCord.

What to try

1. Reset the token. Go to Discord Developer Portal → your application → Bot → Reset Token. Copy the new token. Don’t paste it anywhere else before VibeCord.

2. Check intents. Same page, scroll down to Privileged Gateway Intents — enable Server Members Intent and Message Content Intent if your bot needs them.

3. Re-paste in VibeCord. Open the bot project → Connect Discord → paste the fresh token. Validation runs in under a second.

4. Verify ownership. Make sure the Discord account that owns the application matches the Discord account you signed into VibeCord with. If you handed off ownership, re-claim it in the Developer Portal.

Open Developer Portal

Common mistakes

• Pasting the Application ID instead of the bot token — Application ID is a number; tokens are 70+ chars with dots.
• Pasting the Public Key — that’s for interaction signature verification, not for the bot.
• Pasting the Client Secret — that’s for OAuth, not bot login.
• Adding extra whitespace — strip leading/trailing spaces before pasting.

When to contact support

If you reset the token, copied it directly into VibeCord, and still see BOT_TOKEN_INVALID:

• Drop a screenshot in Discord — make sure to redact the token in the screenshot
• Or email support@vibecord.dev with your account email and the bot’s Application ID (NOT the token)

We can check whether Discord’s API is rate-limiting us or whether the validation flow has a bug.