Discord error 20012: Not authorized to perform this action on this application

The token you used is valid, but it does not have authority over the application named in the request. This is about ownership of the Discord application, not about permissions inside a server. It appears on the application-level endpoints: registering or editing slash commands, managing application emoji, editing the application object, role connection metadata, and similar routes that take /applications/{application.id}/.

The usual root cause is a mismatch between the bot token and the application ID. A bot token belongs to exactly one application. If your deploy script hard-codes a different application ID (a teammate's app, an old app, a typo), Discord authenticates you successfully and then refuses because you are not the owner of the app you are trying to change.

It can also occur when using a user OAuth2 token on application routes where only the bot token or the owning user is allowed.

{
  "message": "You are not authorized to perform this action on this application",
  "code": 20012
}

Derive the application ID at startup from the token (GET /oauth2/applications/@me or from the READY payload's application.id) instead of configuring it separately. That makes a token/app mismatch impossible.

Multi-environment setups avoid this class of bug by never sharing IDs between apps: one application, one token, one env file. If the mismatch is between scopes rather than applications, the failure is 50026; command registration quotas are on the Discord limits page.