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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Telegram

Telegram Getting Updates API

Methods for receiving incoming updates from Telegram

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Getting Updates. 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 4 operations across 4 paths, and defines 8 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}.

4 operations 4 paths 8 schemas 4 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
Contact
Telegram Support
License
Terms of Service
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Telegram Getting Updates 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 4

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

Getting Updates 4

Methods for receiving incoming updates from Telegram

POST
/getUpdates
Get Updates
getUpdates body → 200
POST
/setWebhook
Set Webhook
setWebhook body → 200
POST
/deleteWebhook
Delete Webhook
deleteWebhook body → 200
POST
/getWebhookInfo
Get Webhook Info
getWebhookInfo → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Chat (9 properties), WebhookInfo (8 properties), User (7 properties), Message (6 properties). Each schema is shown below with its type and property counts.

User
object
7 properties 3 required
UpdatesResponse
object
2 properties
Update
object
4 properties 1 required
WebhookInfo
object
8 properties 3 required
Chat
object
9 properties 2 required
WebhookInfoResponse
object
2 properties
Message
object
6 properties 3 required
BooleanResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

telegram-getting-updates-api-openapi.yml Raw ↑

Other APIs Telegram publishes across the network.

Telegram TDLib (Telegram Database Library)
AE Profile APIs.io
Telegram Bot Info API
AE Profile APIs.io
Telegram Chat Management API
AE Profile APIs.io
Telegram Invites API
AE Profile APIs.io
Telegram Member Management API
AE Profile APIs.io
Telegram Message Editing API
AE Profile APIs.io
Telegram Messaging API
AE Profile APIs.io
Telegram Payments API
AE Profile APIs.io
Telegram Stickers API
AE Profile APIs.io
#Getting Updates
← Back to T APIs
API Details
ID
telegram:telegram-getting-updates-api
Base URL
https://api.telegram.org/bot{token}
Docs
https://core.telegram.org/bots/api
Provider
Telegram
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=telegram-getting-updates-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/telegram-getting-updates-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Telegram Getting Updates 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.