This release is a pre-release and may not be stable for production use.
Aptos Python SDK
The official Python SDK for interacting with the Aptos blockchain. Get started with the integration guide.
Note: The sync client is deprecated. Please use the async client for all new projects.
Installation
pip install aptos-sdk
Quickstart
import asyncio
from aptos_sdk.account import Account
from aptos_sdk.async_client import FaucetClient, RestClient
async def main():
rest_client = RestClient("https://fullnode.devnet.aptoslabs.com/v1")
faucet_client = FaucetClient("https://faucet.devnet.aptoslabs.com", rest_client)
# Create and fund two accounts
alice = Account.generate()
bob = Account.generate()
await faucet_client.fund_account(alice.address(), 100_000_000)
await faucet_client.fund_account(bob.address(), 0)
# Transfer 1_000 octas from Alice to Bob
txn_hash = await rest_client.bcs_transfer(alice, bob.address(), 1_000)
await rest_client.wait_for_transaction(txn_hash)
print(f"Bob's balance: {await rest_client.account_balance(bob.address())}")
await rest_client.close()
asyncio.run(main())
API Overview
| Class | Description |
|---|---|
RestClient |
Async client for the Aptos REST API (accounts, transactions, events, blocks). |
FaucetClient |
Funds accounts on devnet/testnet via the faucet service. |
Account |
Represents a keypair and address; supports Ed25519 and Secp256k1. |
AccountAddress |
32-byte account address with AIP-40 compliant formatting. |
EntryFunction |
Constructs Move entry function payloads for submission. |
PackagePublisher |
Publishes and upgrades Move packages, with large-package chunking support. |
Development
Requirements
This SDK uses uv for packaging and dependency management:
curl -LsSf https://astral.sh/uv/install.sh | sh
uv sync --extra dev
Unit testing
make test
E2E testing and Using the Aptos CLI
- Download and install the Aptos CLI.
- Set the environment variable
APTOS_CLI_PATHto the full path of the CLI. - Retrieve the Aptos Core Github Repo (git clone https://github.com/aptos-labs/aptos-core)
- Set the environment variable
APTOS_CORE_REPOto the full path of the Repository. make integration_test
You can do this a bit more manually by:
First, run a local testnet (run this from the root of aptos-core):
aptos node run-local-testnet --force-restart --assume-yes --with-indexer-api
Next, tell the end-to-end tests to talk to this locally running testnet:
export APTOS_CORE_REPO="/path/to/repo"
export APTOS_FAUCET_URL="http://127.0.0.1:8081"
export APTOS_INDEXER_URL="http://127.0.0.1:8090/v1/graphql"
export APTOS_NODE_URL="http://127.0.0.1:8080/v1"
Finally run the tests:
make examples
Integration Testing Using the Aptos CLI:
make integration_test
Autoformatting
make fmt
Autolinting
make lint
Package Publishing
- Download the Aptos CLI.
- Set the environment variable
APTOS_CLI_PATHto the full path of the CLI. uv run python -m aptos_sdk.cliand set the appropriate command-line parameters
Semantic versioning
This project follows semver as closely as possible
Metadata
Release files for aptos-sdk-fork 0.12.0a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aptos_sdk_fork-0.12.0a4.tar.gz | 74.4 kB | With provenance | Details for aptos_sdk_fork-0.12.0a4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aptos_sdk_fork-0.12.0a4-py3-none-any.whl | Python 3 | none | any | Details for aptos_sdk_fork-0.12.0a4-py3-none-any.whl |
Total release size: 175.0 kB
Release files / aptos_sdk_fork-0.12.0a4.tar.gz
| Download URL | aptos_sdk_fork-0.12.0a4.tar.gz |
|---|---|
| Size | 74.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abb10f213713b58008490535b8238fe6ddedfbf4289676fb72c106261f2465a2
|
|
BLAKE2b-256 checksum How to use checksums |
516c9b93c98be8c2e086c471b2334e2dffe87c46578a0ce322dbbdada336e7d8
|
| 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 Sep 10, 2026.
Transparency logRelease files / aptos_sdk_fork-0.12.0a4-py3-none-any.whl
| Download URL | aptos_sdk_fork-0.12.0a4-py3-none-any.whl |
|---|---|
| Size | 100.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b40f3973a20440d4d49e506d4542ba375e43eab1c63b058e6f5b8f093a32069
|
|
BLAKE2b-256 checksum How to use checksums |
3759e19f7472a78b5678d33ec504156523af8da2d3823669dab58b3b1e9dd5e6
|
| 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 Sep 10, 2026.
Transparency logSecurity for aptos-sdk-fork 0.12.0a4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aptos_sdk_fork-0.12.0a4.tar.gz
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 Sep 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.