An Alchemy SDK to use the Alchemy API.
❗❗ THIS LIBRARY IS IN EARLY ALPHA ❗❗
This library is in active development and does not follow semantic versioning. Breaking changes may be introduced at any time. Please use with caution.
The SDK supports the exact same syntax and functionality of the Web3 eth
,
making it a 1:1 mapping for anyone using the Web3 eth
library. However, it adds a
significant amount of improved functionality on top of Web3, such as easy
access to Alchemy’s Enhanced and NFT APIs, and quality-of-life improvements
such as automated retries.
The SDK leverages Alchemy's hardened node infrastructure, guaranteeing best-in-class node reliability, scalability, and data correctness, and is undergoing active development by Alchemy's engineers.
🙋♀️ FEATURE REQUESTS:
We'd love your thoughts on what would improve your web3 dev process the most! If you have 5 minutes, tell us what you want on our Feature Request feedback form, and we'd love to build it for you.
The SDK currently supports the following chains:
Use the package manager pip to install alchemy-sdk.
pip3 install alchemy-sdk
After installing the app, you can then import and use the SDK:
from alchemy import Alchemy, Network
# create Alchemy object using your Alchemy api key, default is "demo"
api_key = "your_api_key"
# choose preferred network from Network, default is ETH_MAINNET
network = Network.ETH_MAINNET
# choose the maximum number of retries to perform, default is 5
max_retries = 3
# create Alchemy object
alchemy = Alchemy(api_key, network, max_retries=max_retries)
ℹ️ Creating a unique Alchemy API Key
The public "demo" API key may be rate limited based on traffic. To create your own API key, sign up for an Alchemy account here and use the key created on your dashboard for the first app.
The Alchemy SDK currently supports 2 different namespaces, including:
core
: All web3.eth methods and Alchemy Enhanced API methodsnft
: All Alchemy NFT API methodsIf you are already using web3.eth, you should be simply able to replace the web3.eth object with alchemy.core
and it should work properly.
ℹ️ ENS Name Resolution
The Alchemy SDK supports ENS names (e.g.
vitalik.eth
) for every parameter where you can pass in a Externally Owned Address, or user address (e.g.0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
).
from alchemy import Alchemy
alchemy = Alchemy()
# Access standard Web3 request. Gets latest block hash
block_hash = Alchemy.to_hex(alchemy.core.get_block('latest')['hash'])
# Access Alchemy Enhanced API requests. Gets all transaction receipts for a given block hash.
alchemy.core.get_transaction_receipts(block_hash=block_hash)
# Access the Alchemy NFT API. Gets contract metadata for NFT and gets collection name
contract = "0x01234567bac6ff94d7e4f0ee23119cf848f93245"
print(alchemy.nft.get_contract_metadata(contract).opensea_metadata.collection_name)
The Alchemy class also supports static methods from Web3 object that streamline the development process:
to_bytes
, to_int
, to_hex
, to_text
, to_json
, keccak
to_wei
, from_wei
is_address
, is_checksum_address
, to_checksum_address
The core namespace contains all commonly-used Web3.eth methods.
It also includes the majority of Alchemy Enhanced APIs, including:
get_token_metadata()
: Get the metadata for a token contract address.get_token_balances()
: Gets the token balances for an owner given a list of contracts.get_asset_transfers()
: Get transactions for specific addresses.get_transaction_receipts()
: Gets all transaction receipts for a given block.The SDK currently supports the following NFT API endpoints
under the alchemy.nft
namespace:
get_nft_metadata()
: Get the NFT metadata for an NFT contract address and tokenId.get_nft_metada_batch()
: Get the NFT metadata for multiple NFT contract addresses/token id pairs.get_contract_metadata()
: Get the metadata associated with an NFT contract.get_contract_metadata_batch()
: Get the metadata associated with multiple NFT contracts in a single request.get_contracts_for_owner()
: Get all NFT contracts that the provided owner address owns.get_nfts_for_owner()
: Get NFTs for an owner address.get_nfts_for_contract()
: Get all NFTs for a contract address.get_owners_for_nft()
: Get all the owners for a given NFT contract address and a particular token ID.get_owners_for_contract()
: Get all the owners for a given NFT contract address.get_minted_nfts()
: Get all the NFTs minted by the owner address.get_transfers_for_owner()
: Get all the NFT transfers for a given owner address.get_transfers_for_contract()
: Get all the NFT transfers for a given NFT contract address.verify_nft_ownership()
: Check whether the provided owner address owns the provided NFT contract addresses.is_spam_contract()
: Check whether the given NFT contract address is a spam contract as defined by Alchemy (see the NFT API FAQ)get_spam_contracts()
: Returns a list of all spam contracts marked by Alchemy.refresh_nft_metadata()
: Refresh the cached NFT metadata for a contract address and a single tokenId.refresh_contract()
: Enqueues the specified contract address to have all token ids' metadata refreshed.get_floor_price()
: Return the floor prices of a NFT contract by marketplace.compute_rarity()
: Get the rarity of each attribute of an NFT.get_nft_sales()
: Returns NFT sales that have happened through on-chain marketplaces.summarize_nft_attributes()
: Get the summary of attribute prevalence for all NFTs in a contract.search_contract_metadata()
: Search for a keyword across metadata of all ERC-721 and ERC-1155 smart contracts.The Alchemy NFT endpoints return 100 results per page. To get the next page, you can pass in
the page_key
returned by the previous call.
The NFT API in the SDK standardizes response types to reduce developer friction, but note this results in some differences compared to the Alchemy REST endpoints:
Collection
have been renamed to use the name Contract
for greater accuracy: e.g. get_nfts_for_contract
.get_nfts_for_owner()
is alchemy_getNfts
, get_owners_for_nft()
is alchemy_getOwnersForToken
).omit_metadata
parameter (vs. withMetadata
).page_key
parameter for pagination (vs. nextToken
/startToken
)token_uri
fields are omitted.BaseNft
and Nft
.Nft
object.Nft
object are named differently than the REST response.Below are a few usage examples.
from alchemy import Alchemy
from alchemy.nft import NftFilters
alchemy = Alchemy()
# Get how many NFTs an address owns.
response = alchemy.nft.get_nfts_for_owner('vitalik.eth')
print(response['total_count'])
# Get all the image urls for all the NFTs an address owns.
for nft in response['owned_nfts']:
print(nft.image)
# Filter out spam NFTs.
nfts_without_spam = alchemy.nft.get_nfts_for_owner('vitalik.eth', exclude_filters=[NftFilters.SPAM])
from alchemy import Alchemy
alchemy = Alchemy()
# Bored Ape Yacht Club contract address.
bayc_address = '0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D'
# Omit the NFT metadata for smaller payloads.
response = alchemy.nft.get_nfts_for_contract(bayc_address, omit_metadata=True, page_size=5)
for nft in response['nfts']:
owners = alchemy.nft.get_owners_for_nft(
contract_address=nft.contract_address, token_id=nft.token_id
)
print(f"owners: {owners}, tokenId: {nft.token_id}")
from alchemy import Alchemy
alchemy = Alchemy()
print(alchemy.core.get_token_balances('vitalik.eth'))
If you have any questions, issues, or feedback, please file an issue on GitHub, or drop us a message on our Discord channel for the SDK.