Discord error 50014: Invalid authentication token provided

A token was sent, Discord parsed it, and it is not valid. Either it never was (typo, truncated copy, wrong string entirely) or it was valid once and has since been reset. Discord invalidates a bot token when you click Reset Token in the Developer Portal, when the token is detected in a public place such as a GitHub repository, and when the application is deleted or transferred in some flows.

Compare 40001 (no token at all) and gateway 4004 (same bad-token condition, but on the WebSocket). If you see 4004 on connect and 50014 on REST, it is one problem: the token in your environment is not the current one.

Tokens are long base64-ish strings with two dots. A token missing its last few characters still looks plausible, which is why "I copied it correctly" is usually wrong.

{
  "message": "401: Unauthorized",
  "code": 0
}

// documented example for this code:
{
  "message": "Invalid authentication token",
  "code": 50014
}

Store the token in a secrets manager and inject it at runtime; never commit it. Add a pre-commit hook or secret scanner to the repository. Keep one token per environment and name the env vars so dev and prod cannot be confused.