BitcoinAverage PIP Library
The following examples demonstrate how Http and Websocket requests are made. Just enter your public key and you can run the examples.
Get your api key by logging in here: https://pro.bitcoinaverage.com/
Official documentation: https://apiv2.bitcoinaverage.com
More examples on Github: https://github.com/bitcoinaverage/api-integration-examples/
Http example
from bitcoinaverage import RestfulClient
if __name__ == '__main__':
public_key = 'your_public_key'
restful_client = RestfulClient(public_key)
ticker_global_per_symbol = restful_client.ticker_global_per_symbol('BTCUSD')
print('Global Ticker for BTCUSD:')
print(ticker_global_per_symbol)
Websocket V1 example
from bitcoinaverage import TickerWebsocketClient
if __name__ == '__main__':
public_key = 'your_public_key'
print('Connecting to the ticker websocket...')
ws = TickerWebsocketClient(public_key)
ws.ticker_data('local', 'BTCUSD')
Websocket V2 examples
Version 2 the websocket clients accept a list of cryptocurrencies and a list of exchange respectively. They also use new optimized algorithm for quicker updates.
Ticker
from bitcoinaverage import TickerWebsocketClientV2
if __name__ == '__main__':
public_key = 'your_public_key'
print('Connecting to the ticker websocket...')
ws = TickerWebsocketClientV2(public_key)
ws.ticker_data('local', ['BTCUSD', 'ETHUSD'])
Exchanges
from bitcoinaverage import ExchangeWebsocketClientV2
if __name__ == '__main__':
public_key = 'your_public_key'
print('Connecting to the exchange websocket...')
ws = ExchangeWebsocketClientV2(public_key)
ws.exchange_data(['bitstamp', 'coinbasepro'])
Copyright Blockchain Data LTD
Metadata
Release files for bitcoinaverage 0.3.1
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 | |
|---|---|---|---|---|
| bitcoinaverage-0.3.1.tar.gz | 15.7 kB | Without provenance | Details |
Security for bitcoinaverage 0.3.1
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.