Applications
The Applications section is used to create your own API applications, configure their permissions, and issue tokens.
In this model, an application:
- belongs to your account
- has its own
ID - has a set of available permissions
- can issue one or more tokens
- can be linked to one or more chats
It is important to distinguish three entities:
- application — a container with a name and a list of available permissions
- token — a secret key issued inside the application
- chat link — permission to use a specific application in a specific chat with a separate set of allowed permissions
Where This Section Is
- Open the bot in private messages.
- Open
/settings. - Go to
Private Settings. - Open
My applications.
This is where applications themselves are created and managed. It is not a setting of a specific chat.
How to Create an Application
- Open
My applications. - Click the application creation button.
- Send the application name as a regular message.
After that, the application will appear in the main list.
It is better to use clear names so it is obvious where and why the application is used. For example: Moderation Dashboard, Internal Bot, Analytics Sync.
What Is in the Application Card
The application card shows:
- the application name
- its
ID - the list of tokens, if any have already been issued
From the same card, you can:
- manage application permissions
- issue a new token
- open a token card
- delete the application
How Application Permissions Work
The permissions selected on the application define the upper bound of what can later be granted to tokens and chats.
If a permission is not enabled on the application itself:
- it cannot be granted to a token
- it cannot be used for that application when linking it to a chat
So the usual order is:
- first create the application
- then enable the required permissions on it
- then issue a token
- then link the application to a chat and choose which permissions should actually be available in that chat
How to Issue a Token
- Open the required application.
- Click the token issuance button.
- Send the token name.
- Select the token permissions.
- Confirm creation.
A token can only receive permissions that are already enabled on the application itself.
After creation, the bot sends the token value in a separate message.
Important Notes About Tokens
- a token does not need to receive all application permissions
- it is better to issue separate tokens for different integrations
- the token value is shown at creation time, so it should be saved in your system immediately
- unused tokens should be deleted so unnecessary keys do not remain active
More details: Tokens
Deleting an Application
You should delete an application only if it is no longer used anywhere.
Before deleting, check:
- whether an external service still uses this application
- whether it still has active tokens
- whether it is still linked to chats where it should continue working
If you only need to remove the application from a specific chat, it is usually enough to remove the chat link instead of deleting the whole application.
More details: Linked Applications
Recommended Setup Order
If you are setting up an integration from scratch, the most practical order is:
- create the application in private settings
- enable the required permissions on it
- issue a separate token for the specific integration
- link the application to the required chat
- during linking, leave only the permissions that are actually needed in that chat
This makes access management easier and makes it clearer which token is used for what.