Canonical source for Telegram API data.
This repository collects, normalizes, and publishes structured data for Telegram APIs, including Bot API, MTProto, Telegram Desktop, and TDLib. The generated artifacts are consumed by other projects in the tgapis ecosystem.
Credits and original intent are preserved from earlier revisions of this repository.
-
Telethon TL Documentation
https://tgapis.github.io/x/Telegram/ -
Bot API Docs Explorer
https://tgapis.github.io/botapidocs/ -
Interactive TL-Schema Explorer
https://telegramplayground.github.io/schema.tl/ -
Telethon Diff (fork of diff.telethon.dev)
- Telegram Desktop: https://tgapis.github.io/x/TL/diff/tdesktop.html
- TDLib: https://tgapis.github.io/x/TL/diff/tdlib.html
-
botapi.json
https://tgapis.github.io/x/botapi.json
↗ -
botapi.min.json
https://tgapis.github.io/x/botapi.min.json
↗ -
api.json
https://tgapis.github.io/x/api.json
↗ -
core.json
https://tgapis.github.io/x/core.json
↗ -
corefork.json
https://tgapis.github.io/x/corefork.json
↗ -
tdesktop.json
https://tgapis.github.io/x/tdesktop.json
↗ -
tdlib.json
https://tgapis.github.io/x/tdlib.json
↗ -
blogfork.json
https://tgapis.github.io/x/blogfork.json
↗
-
api.tl
https://raw.githubusercontent.com/tgapis/x/data/api.tl -
core.tl
https://raw.githubusercontent.com/tgapis/x/data/core.tl -
corefork.tl
https://raw.githubusercontent.com/tgapis/x/data/corefork.tl -
tdesktop.tl
https://raw.githubusercontent.com/tgapis/x/data/tdesktop.tl -
tdlib.tl
https://raw.githubusercontent.com/tgapis/x/data/tdlib.tl -
blogfork.tl
https://raw.githubusercontent.com/tgapis/x/data/blogfork.tl
Data is extracted and derived from official Telegram sources:
-
Telegram Bot API
https://core.telegram.org/bots/api -
Bot API / MTProto API
https://core.telegram.org/ -
Telegram Desktop API
https://github.com/telegramdesktop/tdesktop -
TDLib API
https://github.com/tdlib/td
This repository follows a clear and verifiable lineage:
- https://github.com/PaulSonOfLars/telegram-bot-api-spec
- https://github.com/TelegramPlayground/TG-APIs
- tgapis/x — Ankit Chaubey
The data, structure, and intent are directly inherited and continuously evolved from the above projects, making this a true downstream continuation rather than an unrelated reimplementation.