Key concepts

API ID, API Hash and Bot Token: what is the difference?

Distinguish application credentials from bot tokens and verification codes so you choose the right service and fill in the right fields.

GetTGAPI editorial teamUpdated

Quick answer: ID and Hash come from your developer application. A Bot Token is for a bot; they are not interchangeable. GetTGAPI can help identify the credentials you need before assisting with the portal application.

For help, contact support at gettgapi.com/en/help#contact. Already have an access code? Start at gettgapi.com/en/redeem.

Check what your tool requires

Fields named api_id and api_hash usually mean Telegram application credentials. A Bot Token field usually means a Telegram Bot API integration. Neither can replace the other.

Do not buy solely because a tool says Telegram API. Read its configuration instructions. If unsure, give support the non-secret field names.

API ID and API Hash

API ID identifies an application. API Hash is its associated credential. They come from the developer portal and are generally used together.

They are not phone verification codes or two-step passwords. Accessing a user account also requires user authorization: getting ID and Hash does not log in that user. Telegram user authorization

API ID is not an order number and API Hash is not a one-time code. Copy each value into its own field, without labels, quotes or explanatory text.

Bot Token

A Bot Token authorizes a bot to call the Bot API and is managed through official BotFather. Support bots and other bot functions use this type of credential.

Follow Telegram's BotFather instructions to create or manage bots. Our website service delivers API ID and API Hash; it does not replace BotFather or sell bot tokens.

Verification codes and two-step passwords

A developer portal code verifies access to that portal. A Telegram client login code belongs to the particular client login request. Do not mix them. Accounts with two-step verification may also need their password when authorizing a client.

GetTGAPI handles the developer portal flow and does not require that password. Support needs no verification codes. If you encounter an unexpected request, stop and describe the page wording without sharing secrets.

Choose your next step

  • Need ID and Hash: use the official portal guide or our assistance service.
  • Applied before but lost your copy: retrieve the existing app.
  • Need a Bot Token: use official BotFather.
  • Asked for a session file or login password: that is the tool's own account authorization process, not the API credentials we deliver.