Helius APIs Python SDK
Python SDK for interacting with the Official Helius APIs - https://docs.helius.xyz/api-reference/.
Installation
Installing Using PIP (Recommended)
pip install helius
Installing from Source
-
Clone the repository:
git clone https://github.com/vmpyre/helius_sdk.git -
Change into the project directory:
cd helius_sdk -
Install the dependencies:
pip install -r requirements.txt
Usage
First, import the SDK's classes for the APIs you'd like to use.
>> from helius import NFTAPI, NameAPI, BalancesAPI, WebhooksAPI, TransactionsAPI
Then, create instances of the classes to interact with the corresponding API endpoints (in this case the BalancesAPI class):
>> balances_api = BalancesAPI("<API_KEY_HERE>")
Generate your API Key from here: https://docs.helius.xyz/introduction/generate-an-api-key
For example, you can use the get_balances() method of the BalancesAPI class to retrieve native Solana balance (in lamports) and all token balances for a given address:
>> balances_api.get_balances("<SOLANA_WALLET_ADDRESS_HERE>")
The SDK provides functionality for interacting with the NFTAPI, NameAPI, BalancesAPI, TransactionsAPI and WebhooksAPI endpoints. You can view the class methods below:
Documentation
WebhooksAPI
NFTAPI
TransactionsAPI
BalancesAPI
NameAPI
See the Official Helius documentation for additional information: https://docs.helius.xyz/api-reference/
Contribution
Feel free to open issues, pull requests and submit feedback. We appreciate your help!
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgements
Thanks to the Helius team for providing an amazing product.
Disclaimer
The developer of this SDK is not part of Helius team and this SDK was submitted for the LamportDAO Hackathon. The developer is not responsible for any errors or issues that may occur when using this SDK. Use at your own risk and feel free to report issues.
Metadata
Release files for helius 0.0.3
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 |
|---|---|---|---|---|
| helius-0.0.3.tar.gz | 5.7 kB | Without provenance | Details for helius-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| helius-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for helius-0.0.3-py3-none-any.whl |
Total release size: 12.5 kB
Release files / helius-0.0.3.tar.gz
| Download URL | helius-0.0.3.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f1f82e28dcc21b5e93d5a137e8e1d11004ebc8cbd2c63169f55e422a9a35640
|
|
BLAKE2b-256 checksum How to use checksums |
fe5c48ccd7418e4911f0bec86c3f493f30e76fe7a9f58ada1ccc09a12c6ca15f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / helius-0.0.3-py3-none-any.whl
| Download URL | helius-0.0.3-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4335571848091c40cc75f4d0e8487a6ffdf2ba5757a5b3ee254374f7aa0a4eac
|
|
BLAKE2b-256 checksum How to use checksums |
4a4a6d921b9784a109a1cfefd7a74da3f69c434654abaafe6deb73f211b68468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for helius 0.0.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.