A modern, easy-to-use, feature-rich, and async-ready API wrapper for Discord’s user API written in Python.
Rapptz for the original library this fork is based on. Without it, the project would not exist.
arandomnewaccount for help when the project was first started.
Key Features
Modern Pythonic API using async and await.
Proper rate limit handling.
Optimised in both speed and memory.
Mostly compatible with the upstream discord.py.
Prevents user account automation detection.
Implements vast amounts of the user account-specific API. For a non-exhaustive list:
Sessions
Read states
Connections
Relationships
Experiments
Protobuf user settings
Application/team management
Store/SKUs/entitlements
Billing (e.g. subscriptions, payments, boosts, promotions, etc.)
Interactions (slash commands, buttons, etc.)
Installing
Python 3.10 or higher is required.
To install the library without full voice support, you can just run the following command:
# Linux/macOS
python3 -m pip install -U discord.py-self
# Windows
py -3 -m pip install -U discord.py-self
Otherwise to get voice support you should run the following command:
# Linux/macOS
python3 -m pip install -U "discord.py-self[voice]"
# Windows
py -3 -m pip install -U discord.py-self[voice]
To install the development version, do the following:
$ git clone https://github.com/dolfies/discord.py-self
$ cd discord.py-self
$ python3 -m pip install -U .[voice]
Optional Packages
PyNaCl (for voice support)
Please note that on Linux installing voice you must install the following packages via your favourite package manager (e.g. apt, dnf, etc) before running the above commands:
libffi-dev (or libffi-devel on some systems)
python-dev (e.g. python3.6-dev for Python 3.6)
Using with Upstream
If you would like to use the library alongside upstream discord.py, you can install selfcord.py instead of discord.py-self. Check out the renamed branch for more information.
Quick Example
import discord
class MyClient(discord.Client):
async def on_ready(self):
print('Logged on as', self.user)
async def on_message(self, message):
# only respond to ourselves
if message.author != self.user:
return
if message.content == 'ping':
await message.channel.send('pong')
client = MyClient()
client.run('token')
Bot Example
import discord
from discord.ext import commands
bot = commands.Bot(command_prefix='>', self_bot=True)
@bot.command()
async def ping(ctx):
await ctx.send('pong')
bot.run('token')
You can find more examples in the examples directory.
Links
Release files for discord.py-self 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| discord_py_self-2.1.0.tar.gz | 1.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| discord_py_self-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 MB
Release files / discord_py_self-2.1.0.tar.gz
| Download URL | discord_py_self-2.1.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bc6d87711e9345784f2ed23cabbe63eba9673008e5b460aa25e3546570bcd07
|
|
BLAKE2b-256 checksum How to use checksums |
c7370a319b6465183a01d245ecdae99d59503bad41ed1176cd7e6943306a5949
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 18, 2026.
Transparency logRelease files / discord_py_self-2.1.0-py3-none-any.whl
| Download URL | discord_py_self-2.1.0-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42abda55168f1c1a2b585a16906d3aefd390d98238d6fc0e5fa586009f54204b
|
|
BLAKE2b-256 checksum How to use checksums |
32f158be56fe81619543e72503aa77727e07fa14623bd8760876e7f107a4e276
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 18, 2026.
Transparency log