We have made you a wrapper you can’t refuse
We have a vibrant community of developers helping each other in our Telegram group. Join us!
Stay tuned for library updates and new releases on our Telegram Channel.
This library provides a pure Python, asynchronous interface for the Telegram Bot API. It’s compatible with Python versions 3.7+.
In addition to the pure API implementation, this library features a number of high-level classes to
make the development of bots easy and straightforward. These classes are contained in the
A pure API implementation without
telegram.ext is available as the standalone package
python-telegram-bot-raw. See here for details.
python-telegram-bot-raw in conjunction will result in undesired side-effects, so only install one of both.
Telegram API support¶
All types and methods of the Telegram Bot API 6.4 are supported.
You can install or upgrade
$ pip install python-telegram-bot --upgrade
To install a pre-release, use the
--pre flag in addition.
You can also install
python-telegram-bot from source, though this is usually not necessary.
$ git clone https://github.com/python-telegram-bot/python-telegram-bot $ cd python-telegram-bot $ python setup.py install
We sign all the releases with a GPG key.
The signatures are uploaded to both the GitHub releases page and the PyPI project and end with a suffix
Please find the public keys here.
The keys are named in the format
<first_version>-current.gpg if the key is currently being used for new releases.
In addition, the GitHub release page also contains the sha1 hashes of the release files in the files with the suffix
This allows you to verify that a release file that you downloaded was indeed provided by the
Dependencies & Their Versions¶
python-telegram-bot tries to use as few 3rd party dependencies as possible.
However, for some features using a 3rd party library is more sane than implementing the functionality again.
As these features are optional, the corresponding 3rd party dependencies are not installed by default.
Instead, they are listed as optional dependencies.
This allows to avoid unnecessary dependency conflicts for users who don’t need the optional features.
The only required dependency is httpx[http2] ~= 0.23.3 for
telegram.request.HTTPXRequest, the default networking backend. By default, HTTP/2 is used, as it
provides greater performance and stability, specially for concurrent requests.
python-telegram-bot is most useful when used along with additional libraries.
To minimize dependency conflicts, we try to be liberal in terms of version requirements on the (optional) dependencies.
On the other hand, we have to ensure stability of
python-telegram-bot, which is why we do apply version bounds.
If you encounter dependency conflicts due to these bounds, feel free to reach out.
PTB can be installed with optional dependencies:
pip install python-telegram-bot[passport]installs the cryptography>=3.0 library. Use this, if you want to use Telegram Passport related functionality.
pip install python-telegram-bot[socks]installs httpx[socks]. Use this, if you want to work behind a Socks5 server.
pip install python-telegram-bot[rate-limiter]installs aiolimiter~=1.0.0. Use this, if you want to use
pip install python-telegram-bot[webhooks]installs the tornado~=6.2 library. Use this, if you want to use
pip install python-telegram-bot[job-queue]installs the APScheduler~=3.10.0 library and enforces pytz>=2018.6, where
pytzis a dependency of
APScheduler. Use this, if you want to use the
To install multiple optional dependencies, separate them by commas, e.g.
pip install python-telegram-bot[socks,webhooks].
Additionally, two shortcuts are provided:
pip install python-telegram-bot[all]installs all optional dependencies.
pip install python-telegram-bot[ext]installs all optional dependencies that are related to
[rate-limiter, webhooks, callback-data, job-queue].
Our Wiki contains an Introduction to the API explaining how the pure Bot API can be accessed via
Moreover, the Tutorial: Your first Bot gives an introduction on how chatbots can be easily programmed with the help of the
The wiki is home to number of more elaborate introductions of the different features of
python-telegram-botand other useful resources that go beyond the technical documentation.
Our examples section contains several examples that showcase the different features of both the Bot API and
python-telegram-bot. Even if it is not your approach for learning, please take a look at
echobot.py. It is the de facto base for most of the bots out there. The code for these examples is released to the public domain, so you can start by grabbing the code and building on top of it.
The official Telegram Bot API documentation is of course always worth a read.
If the resources mentioned above don’t answer your questions or simply overwhelm you, there are several ways of getting help.
We have a vibrant community of developers helping each other in our Telegram group. Join us! Asking a question here is often the quickest way to get a pointer in the right direction.
Ask questions by opening a discussion.
You can even ask for help on Stack Overflow using the python-telegram-bot tag.
python-telegram-bot is built on top of Pythons
asyncio is in general single-threaded,
python-telegram-bot does currently not aim to be thread-safe.
Noteworthy parts of
python-telegram-bots API that are likely to cause issues (e.g. race conditions) when used in a multi-threaded setting include:
all classes in the
telegram.ext.filtersmodule that allow to add/remove allowed users/chats at runtime
Occasionally we are asked if we accept donations to support the development. While we appreciate the thought, maintaining PTB is our hobby, and we have almost no running costs for it. We therefore have nothing set up to accept donations. If you still want to donate, we kindly ask you to donate to another open source project/initiative of your choice instead.
You may copy, distribute and modify the software provided that modifications are described and licensed for free under LGPL-3. Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don’t have to be.