How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Telegram Bot Info API

Methods for getting and setting bot information

Telegram Bot Info API is one of 10 APIs that Telegram publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Bot Info. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a GitHub repository, authentication docs, and a changelog.

This API exposes 5 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 9.5.

Requests are made against a single base URL, https://api.telegram.org/bot{token}.

5 operations 5 paths 9 schemas 5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
9.5
Base URL
https://api.telegram.org/bot{token}
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Telegram Bot Info API declares 1 security scheme for authenticating requests. An API key is passed in the path as token (BotToken). By default, every request must be authenticated.

  • BotToken — Bot authentication token obtained from @BotFather (embedded in URL path)

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 POST. Each is listed below with its method, path, parameters, and response codes.

Bot Info 5

Methods for getting and setting bot information

POST
/getMe
Get Bot Info
getMe → 200
POST
/getUserProfilePhotos
Get User Profile Photos
getUserProfilePhotos body → 200
POST
/getFile
Get File
getFile body → 200
POST
/setMyCommands
Set My Commands
setMyCommands body → 200
POST
/getMyCommands
Get My Commands
getMyCommands body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are User (7 properties), File (4 properties), UserProfilePhotos (2 properties), UserProfilePhotosResponse (2 properties). Each schema is shown below with its type and property counts.

User
object
7 properties 3 required
FileResponse
object
2 properties
File
object
4 properties 2 required
BotCommandsResponse
object
2 properties
UserProfilePhotosResponse
object
2 properties
UserProfilePhotos
object
2 properties 2 required
UserResponse
object
2 properties
BotCommand
object
2 properties 2 required
BooleanResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

telegram-bot-info-api-openapi.yml Raw ↑

Other APIs Telegram publishes across the network.

Telegram TDLib (Telegram Database Library)
Telegram Chat Management API
Telegram Getting Updates API
Telegram Invites API
Telegram Member Management API
Telegram Message Editing API
Telegram Messaging API
Telegram Payments API
Telegram Stickers API
Where this information came from

This is an independent, third-party profile of Telegram Bot Info API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.