Telegram API — Docs, OpenAPI & Kin Score

Telegram is a cloud-based instant messaging and voice-over-IP service that provides a comprehensive Bot API for developers to build bots, automate workflows, send notifications, and create interactive experiences on the Telegram platform. The platform supports text messages, media sharing, payments, inline keyboards, inline queries, webhooks, and live location sharing.

Telegram publishes 10 API contracts indexed on the APIs.io network, including Bot Info API, Chat Management API, Getting Updates API, and 7 more. Tagged areas include Bots, Chat, Messaging, Notification, and Payments.

The Telegram catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.

Telegram’s developer surface includes CLI, changelog, sandbox, getting-started guide, FAQ, support, pricing, and 43 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

58.4/100 strong ▲ 20.4 Agent 25/100 agent aware Front door AI 2/6 trace Heartbeat 74/100 alive open core · BSL-1.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract

Bots Chat Messaging Notification Payments Telegram Social Public APIs Chatbots Webhook Mini Apps

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 58.4/100 · strong

Contract Quality 11.3 / 16

Developer Ergonomics 9.9 / 13

Access Clarity 8.6 / 13

Operational Transparency 6.4 / 8

Contract Governance 1.7 / 8

Discoverability 4.4 / 7

Regulatory Posture 3.3 / 15

Open Source Surface 0.0 / 10

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/telegram/"><img src="https://apis.io/badge/telegram/card.svg" alt="Telegram on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Governance scores 22.0 — up to +9.4 composite points
Contract Quality scores 69.8 — up to +7.6 composite points
Access Clarity scores 65.8 — up to +6.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/telegram/apis.yml: open an issue on github.com/api-evangelist/telegram to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Social and Fediverse	mixed	29.4	-	-
Raycast Store Extensions (first-party publishers + community-wrapped products)	mixed	29.4	-	-
APIs.guru OpenAPI Directory (API definition directory)	mixed	29.4	-	-
Flathub Linux App Publishers (company-published, domain-verified Linux desktop apps)	mixed	29.4	-	-
IFTTT Services (service publishers)	mixed	29.4	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

Telegram TDLib (Telegram Database Library)

TDLib is a cross-platform, fully functional Telegram client library for third-party developers. TDLib takes care of all network implementation details, encryption and local data...

Telegram Bot Info API

Methods for getting and setting bot information

Telegram Chat Management API

Methods for managing chats and chat settings

Telegram Getting Updates API

Methods for receiving incoming updates from Telegram

Telegram Invites API

Methods for managing chat invite links

Telegram Member Management API

Methods for managing chat members and administrators

Telegram Message Editing API

Methods for editing and deleting messages

Telegram Messaging API

Methods for sending messages and media

Telegram Payments API

Methods for handling Telegram Payments

Telegram Stickers API

Methods for working with sticker sets

Scroll for all 10

Telegram Bot Bot Info Stickers API

OPEN COLLECTION

Scroll for all 10

Telegram API pricing

Prices published by Telegram.

Plan	Price
Free	at no cost
Paid broadcasts	0.1 Stars per message

Plan details, limits and sources →

Rate limits

Messages to a single chat: In a single chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but
Messages to a group: In a group, bots are not be able to send more than 20 messages per minute.
Bulk notification broadcast: For bulk notifications, bots are not able to broadcast more than about 30 messages per second

All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Telegram Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Telegram Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Telegram Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Telegram Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Telegram Context

12 classes · 31 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

Telegram — bot rules

13 rules · 5 errors 6 warnings 2 info

SPECTRAL

Telegram — jsonschema rules

6 rules · 5 warnings 1 info

SPECTRAL

Telegram API Rules

64 rules · 58 errors 5 warnings 1 info

SPECTRAL

2 properties

JSON SCHEMA

Scroll for all 20

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Telegram Message Structure

0 properties

JSON STRUCTURE

Examples 3

Example request and response payloads for these APIs.

Telegram Get Updates Example

2 fields

EXAMPLE

Telegram Send Message Example

2 fields

EXAMPLE

Telegram Send Poll Example

2 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Telegram Authentication

apiKey · 1 scheme

SECURITY

Telegram Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Telegram Agentic Access

51 operations · 42 acting · 1 human-in-the-loop

51 operations · 42 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Sandbox

Sandbox

Login

GettingStarted

GettingStarted

DeveloperPortal

DeveloperPortal

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

AgenticAccess

AgenticAccess

Design & Contract 12

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

Conventions

Lifecycle

ErrorCatalog

Conformance

Webhooks

Scroll for all 12

Build 7

SDKs, sample code, and the tooling you integrate with

CLI

IntegrationEdges

SDKs

Packages

SourceCode

GitHub

GitHubOrganization

GitHubOrganization

Scroll for all 7

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Authentication

Authentication

Operate 7

Status, limits, changes, and where to get help

ChangeLog

FAQ

ChangeLog

Support

RateLimits

IssueTracker

StatusPage

Scroll for all 7

Commercial 6

Pricing, plans, and the legal terms of use

Pricing

Plans

FinOps

License

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

Newsroom

Newsroom

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

PublicAPIsListing

PublicAPIsListing

Source (apis.yml)

aid: telegram
name: Telegram
description: Telegram is a cloud-based instant messaging and voice-over-IP service that provides a comprehensive Bot API for
  developers to build bots, automate workflows, send notifications, and create interactive experiences on the Telegram platform.
  The platform supports text messages, media sharing, payments, inline keyboards, inline queries, webhooks, and live location
  sharing.
type: Index
deliveryModel:
  model: open-core
  license: BSL-1.0
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
image: https://telegram.org/img/t_logo.png
tags:
- Bots
- Chat
- Messaging
- Notification
- Payments
- Telegram
- Social
- Public APIs
- Chatbots
- Webhook
- Mini Apps
tags_raw:
- Bots
- Chat
- Messaging
- Notifications
- Payments
- Telegram
- Social
- Public APIs
- Chatbots
- Webhooks
- Mini Apps
created: '2025-02-12'
modified: '2026-05-19'
url: https://raw.githubusercontent.com/api-evangelist/telegram/refs/heads/main/apis.yml
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
common:
- type: Spectral
  url: rules/telegram-jsonschema-spectral-rules.yml
- type: Spectral
  url: rules/telegram-bot-rules.yml
- type: Spectral
  url: rules/telegram-rules.yml
- type: JSONLD
  url: json-ld/telegram-context.jsonld
- type: Vocabulary
  url: vocabulary/telegram-vocabulary.yml
- type: Webhooks
  url: asyncapi/telegram-webhooks.yml
- type: DataModel
  url: data-model/telegram-data-model.yml
- type: CLI
  url: cli/telegram-cli.yml
- type: ChangeLog
  url: changelog/telegram-changelog.yml
- type: Conventions
  url: conventions/telegram-conventions.yml
- type: Sandbox
  url: sandbox/telegram-sandbox.yml
- type: Lifecycle
  url: lifecycle/telegram-lifecycle.yml
- type: ErrorCatalog
  url: errors/telegram-problem-types.yml
- type: Conformance
  url: conformance/telegram-conformance.yml
- type: LLMsTxt
  url: llms/telegram-llms.txt
- type: Hosts
  url: hosts/telegram-hosts.yml
- type: IntegrationEdges
  url: integrations/telegram-integration-edges.yml
- type: SDKs
  url: packages/telegram-packages.yml
- type: Packages
  url: packages/telegram-packages.yml
- type: Login
  url: https://core.telegram.org/widgets/login
- type: GettingStarted
  url: https://core.telegram.org/bots/tutorial
- type: FAQ
  url: https://core.telegram.org/bots/faq
- type: Webhooks
  url: https://core.telegram.org/bots/webhooks
- type: ChangeLog
  url: https://core.telegram.org/bots/api-changelog
- type: Support
  url: https://t.me/botsupport
- type: Newsroom
  url: https://telegram.org/press
- type: SourceCode
  url: https://github.com/tdlib/telegram-bot-api
- type: Pricing
  url: https://core.telegram.org/bots/faq#my-bot-is-hitting-limits-how-do-i-avoid-this
- type: PublicAPIsListing
  url: https://github.com/public-apis/public-apis
- type: Plans
  url: plans/telegram-plans-pricing.yml
- type: RateLimits
  url: rate-limits/telegram-rate-limits.yml
- type: FinOps
  url: finops/telegram-finops.yml
- type: Website
  url: https://www.telegram.org/
- type: IssueTracker
  url: https://github.com/tdlib/td/issues
- type: License
  name: BSL-1.0
  url: https://github.com/tdlib/td/blob/master/LICENSE
- type: AgenticAccess
  url: agentic-access/telegram-agentic-access.yml
- type: DomainSecurity
  url: security/telegram-domain-security.yml
- type: Authentication
  url: authentication/telegram-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/telegram-messenger
- type: Authentication
  url: https://core.telegram.org/bots/api#authorizing-your-bot
- type: TermsOfService
  url: https://telegram.org/tos
- type: PrivacyPolicy
  url: https://telegram.org/privacy
- type: DeveloperPortal
  url: https://core.telegram.org
- type: StatusPage
  url: https://downdetector.com/status/telegram/
- type: Blog
  url: https://telegram.org/blog
- type: GitHub
  url: https://github.com/tdlib
- type: DeveloperPortal
  url: https://core.telegram.org/bots
- type: Documentation
  url: https://core.telegram.org/bots
- type: APIReference
  url: https://core.telegram.org/bots/api
- type: GitHubOrganization
  url: https://github.com/TelegramMessenger
apis:
- aid: telegram:telegram-tdlib
  name: Telegram TDLib (Telegram Database Library)
  description: TDLib is a cross-platform, fully functional Telegram client library for third-party developers. TDLib takes
    care of all network implementation details, encryption and local data storage, allowing developers to build custom Telegram
    clients. It is open source, written in C++, and compatible with virtually any programming language through bindings.
  humanURL: https://core.telegram.org/tdlib
  baseURL: https://core.telegram.org/tdlib
  version: '1.8'
  tags:
  - Client Library
  - Cross-Platform
  - MTProto
  - Open Source
  - Telegram
  tags_raw:
  - Client Library
  - Cross-Platform
  - MTProto
  - Open Source
  - Telegram
  - Open-Source
  properties:
  - type: Documentation
    url: https://core.telegram.org/tdlib
  - type: GettingStarted
    url: https://core.telegram.org/tdlib/getting-started
  - type: GitHubRepository
    url: https://github.com/tdlib/td
  contact:
  - type: GitHub
    url: https://github.com/tdlib/td
- aid: telegram:telegram-bot-info-api
  name: Telegram Bot Info API
  description: Methods for getting and setting bot information
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Bot Info
  properties:
  - type: OpenAPI
    url: openapi/telegram-bot-info-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-bot-command-schema.json
  - type: JSONSchema
    url: json-schema/telegram-bot-commands-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-user-profile-photos-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-file-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-user-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
- aid: telegram:telegram-chat-management-api
  name: Telegram Chat Management API
  description: Methods for managing chats and chat settings
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Chat Management
  properties:
  - type: OpenAPI
    url: openapi/telegram-chat-management-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-chat-members-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-chat-member-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-chat-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-integer-response-schema.json
- aid: telegram:telegram-getting-updates-api
  name: Telegram Getting Updates API
  description: Methods for receiving incoming updates from Telegram
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Getting Updates
  properties:
  - type: OpenAPI
    url: openapi/telegram-getting-updates-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-updates-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-webhook-info-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
- aid: telegram:telegram-invites-api
  name: Telegram Invites API
  description: Methods for managing chat invite links
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Invites
  properties:
  - type: OpenAPI
    url: openapi/telegram-invites-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-chat-invite-link-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-string-response-schema.json
- aid: telegram:telegram-member-management-api
  name: Telegram Member Management API
  description: Methods for managing chat members and administrators
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Member Management
  properties:
  - type: OpenAPI
    url: openapi/telegram-member-management-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-chat-permissions-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
- aid: telegram:telegram-message-editing-api
  name: Telegram Message Editing API
  description: Methods for editing and deleting messages
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Message Editing
  properties:
  - type: OpenAPI
    url: openapi/telegram-message-editing-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-message-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
- aid: telegram:telegram-messaging-api
  name: Telegram Messaging API
  description: Methods for sending messages and media
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Messaging
  properties:
  - type: OpenAPI
    url: openapi/telegram-messaging-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-message-id-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-message-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
- aid: telegram:telegram-payments-api
  name: Telegram Payments API
  description: Methods for handling Telegram Payments
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/telegram-payments-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-labeled-price-schema.json
  - type: JSONSchema
    url: json-schema/telegram-message-response-schema.json
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json
- aid: telegram:telegram-stickers-api
  name: Telegram Stickers API
  description: Methods for working with sticker sets
  humanURL: https://core.telegram.org/bots/api
  baseURL: https://api.telegram.org/bot{token}
  tags:
  - Stickers
  properties:
  - type: OpenAPI
    url: openapi/telegram-stickers-api-openapi.yml
  - type: Documentation
    url: https://core.telegram.org/bots/api
  - type: GettingStarted
    url: https://core.telegram.org/bots
  - type: GitHubRepository
    url: https://github.com/tdlib/telegram-bot-api
  - type: Authentication
    url: https://core.telegram.org/bots/api#authorizing-your-bot
  - type: ChangeLog
    url: https://core.telegram.org/bots/api-changelog
  - type: FAQ
    url: https://core.telegram.org/bots/faq
  - type: JSONSchema
    url: json-schema/telegram-boolean-response-schema.json

Telegram API — frequently asked questions

Does Telegram have an API?

Yes. APIs.io lists 10 APIs from Telegram, including Telegram TDLib (Telegram Database Library), Telegram Bot Info API and Telegram Chat Management API, and 7 more.

Is there an OpenAPI specification for the Telegram API?

Yes. APIs.io indexes 9 OpenAPI specifications for Telegram, each linked for download from this page.

How do I authenticate with the Telegram API?

Telegram uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Telegram Authentication.

How much does the Telegram API cost?

Telegram publishes its prices; its Free plan is at no cost as of 2026-11-05. APIs.io lists 2 pricing plans for Telegram, with each plan's price, limits and inclusions under Pricing on this page.

Is the Telegram API ready for AI agents?

Telegram has a Kin Score of 58.4 out of 100 (strong) and an Agent Readiness score of 25.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/telegram"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/telegram/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/telegram/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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