Autogenerated from lexicons, well type hinted, documented, sync and async SDK for Python
Documentation
•
Guides
•
Examples
•
Discord Bluesky API
The AT Protocol SDK
⚠️ Under construction. Until the 1.0.0 release compatibility between versions is not guaranteed.
from atproto import Client, client_utils
def main():
client = Client()
profile = client.login('my-handle', 'my-password')
print('Welcome,', profile.display_name)
text = client_utils.TextBuilder().text('Hello World from ').link('Python SDK', 'https://atproto.blue')
post = client.send_post(text)
client.like(post.uri, post.cid)
if __name__ == '__main__':
main()
Code snippet of async version
import asyncio
from atproto import AsyncClient, client_utils
async def main():
client = AsyncClient()
profile = await client.login('my-handle', 'my-password')
print('Welcome,', profile.display_name)
text = client_utils.TextBuilder().text('Hello World from ').link('Python SDK', 'https://atproto.blue')
post = await client.send_post(text)
await client.like(post.uri, post.cid)
if __name__ == '__main__':
asyncio.run(main())
Installing
pip install atproto
Python 3.9 or higher.
What you get
This SDK attempts to implement everything that ATProto provides. There is support for Lexicon schemas, XRPC clients, Firehose, Jetstream, Identity, DID keys, signatures, and more. All models, queries, and procedures are generated automatically. The main focus is on the lexicons of atproto.com and bsky.app, but there is no vendor lock on it. Point the code generator at your own lexicon schemas and it produces the same typed models and clients for them. The SDK also provides utilities to work with CID, NSID, AT URI schemes, DAG-CBOR, CAR files, DID documents and more.
- Sync and async clients with identical method sets.
- Type hints everywhere, so your IDE can navigate the whole protocol.
- A high-level client for common tasks, with the complete XRPC surface underneath it.
- Real-time streaming over the Firehose or Jetstream, including archive backfill.
- Your own lexicons, compiled into an importable package by
atp gen custom.
Documentation
The documentation is live at atproto.blue.
| 🚀 Quickstart | Install, log in, post, read a timeline |
| 📚 Guides | Posting, reading, streaming, identity, errors |
| 💡 Examples | Every runnable example, inlined |
| 🧩 Custom lexicons | Generate models and clients from your own lexicons |
🛠 The atp CLI |
The code generator's command line |
| 💬 Direct messages | Chats, messages, and reactions |
| 🔥 Firehose & Jetstream | Data streaming from the whole network |
| 🌐 Identity | DID and handle resolvers |
| 📖 Model reference | Every lexicon on the network, as a Pydantic model |
| 🍿 Feed generator | Build a custom feed, end to end |
This is the SDK's documentation, not the protocol's. For the protocol itself, see atproto.com and bsky.network/docs.
SDK structure
The SDK is built upon the following components:
| Package | Description |
|---|---|
atproto |
Import shortcuts to other packages. |
atproto_cli |
CLI tool to generate code. |
atproto_client |
XRPC Client, data models, and utils like rich text helper. |
atproto_codegen |
Code generator of models, clients, and namespaces. |
atproto_core |
Tools to work with NSID, AT URI Schemes, CID, CAR files, and DID Documents. |
atproto_crypto |
Crypto utils like multibase, signature verification, work with DID keys. |
atproto_firehose |
Firehose (data streaming) client and models. |
atproto_identity |
Identity resolvers for DID, Handle, AT Protocol data, signing keys. |
atproto_jetstream |
Jetstream v2 (data streaming) client and models. |
atproto_lexicon |
Lexicon parser. |
atproto_server |
Server-side utils like JWT. |
atproto_subscription |
Websocket subscription runtime behind the streaming clients. |
I highly recommend that you use the atproto package to import everything that you need. It contains shortcuts to all other packages.
Getting help
You can get help in several ways:
- Report bugs, request new features by creating an issue.
- Ask questions by starting a discussion.
- Ask questions in Discord server.
Change log
The full change log is available in CHANGES.md.
Contributing
Contributions of all sizes are welcome. The contribution guidelines will be presented later.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for atproto 0.0.73
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| atproto-0.0.73.tar.gz | 325.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atproto-0.0.73-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / atproto-0.0.73.tar.gz
| Download URL | atproto-0.0.73.tar.gz |
|---|---|
| Size | 325.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dc0e7f60ce99113b3371528d368e47566b44344812c7b0047229eda8b07eb13
|
|
BLAKE2b-256 checksum How to use checksums |
1a1b02577f6d5eaa62d7d7fd922ccf6905c77a3f1cf619286690b5fca5da637f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 17, 2026.
Transparency logRelease files / atproto-0.0.73-py3-none-any.whl
| Download URL | atproto-0.0.73-py3-none-any.whl |
|---|---|
| Size | 675.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
772dbef364788385724b1724434a42c56b9aeeec0e480c70f6b7edd7f65f1e77
|
|
BLAKE2b-256 checksum How to use checksums |
980ff2289686a9e0cbadfe268116c9d81886e76354c7d748bb94aa9669a40ed1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 17, 2026.
Transparency log
