asyncprawcore is a low-level communication layer used by Async PRAW 7+.
Installation
Install asyncprawcore with uv via:
uv add asyncprawcore
Alternatively, install using pip via:
pip install asyncprawcore
Execution Example
The following example demonstrates how to use asyncprawcore to obtain the list of trophies for a given user using the script-app type. This example assumes you have the environment variables PRAWCORE_CLIENT_ID and PRAWCORE_CLIENT_SECRET set to the appropriate values for your application.
import os
import pprint
import asyncio
import asyncprawcore
async def main():
authenticator = asyncprawcore.TrustedAuthenticator(
client_id=os.environ["PRAWCORE_CLIENT_ID"],
client_secret=os.environ["PRAWCORE_CLIENT_SECRET"],
requestor=asyncprawcore.Requestor(user_agent="YOUR_VALID_USER_AGENT"),
)
authorizer = asyncprawcore.ReadOnlyAuthorizer(authenticator=authenticator)
await authorizer.refresh()
async with asyncprawcore.session(authorizer=authorizer) as session:
pprint.pprint(
await session.request(method="GET", path="/api/v1/user/bboe/trophies")
)
if __name__ == "__main__":
asyncio.run(main())
Save the above as trophies.py and then execute via:
python trophies.py
Additional examples can be found at: https://github.com/praw-dev/asyncprawcore/tree/main/examples
Documentation
asyncprawcore’s documentation is located at https://asyncprawcore.readthedocs.io/.
Depending on asyncprawcore
asyncprawcore follows semantic versioning with the exception that deprecations will not be preceded by a minor release. In essence, expect only major versions to introduce breaking changes to asyncprawcore’s public interface. As a result, if you depend on asyncprawcore then it is a good idea to specify not only the minimum version of asyncprawcore your package requires, but to also limit the major version.
Below are two examples of how you may want to specify your asyncprawcore dependency:
setup.py
setup(..., install_requires=["asyncprawcore >=0.1, <1"], ...)
requirements.txt
asyncprawcore >=1.5.1, <2
Release files for asyncprawcore 4.0.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 | |
|---|---|---|---|
| asyncprawcore-4.0.0.tar.gz | 1.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asyncprawcore-4.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / asyncprawcore-4.0.0.tar.gz
| Download URL | asyncprawcore-4.0.0.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a95583190c86f14b164dd53190b928883837240f6be30bb4f47c5be3c11d5736
|
|
BLAKE2b-256 checksum How to use checksums |
e9f628bb1cafb664e53d045830593b2442aaf7e8cea2598c2da916d76412abb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jun 13, 2026.
Transparency logRelease files / asyncprawcore-4.0.0-py3-none-any.whl
| Download URL | asyncprawcore-4.0.0-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad3f493a0bde0734b1104b987bfb90169cf4cc3ba107545547f1f992b868e4c1
|
|
BLAKE2b-256 checksum How to use checksums |
a6411b4d9d86465d78829f026693d765aef864025293590ee71f16995eba145a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jun 13, 2026.
Transparency log