Coinbase SDK
Tribulnation SDK implementation for Coinbase.
Installation
pip install tribulnation-coinbase
Recommended account configuration
Coinbase is not a default MarketSDK account. Configure it explicitly and prefer
an authenticated accounts.Coinbase() account, especially for tickers():
authenticated quotes are batched in groups of up to 100 products.
Use accounts.Coinbase(public=True) to allow a credential-free fallback. The router
still prefers resolved credentials when available. Without credentials, tickers()
makes one public book request per selected product, so pass market IDs
to limit request volume. Authentication failures never trigger an automatic switch
to public endpoints.
Ticker quotes and product identity
spot represents Coinbase Advanced Trade spot products. IDs remain native Advanced
Trade product IDs, such as BTC-USD. INTX perpetuals are not supported: Coinbase
retires them on the Advanced Trade API on 2026-10-01, moving international
derivatives to a Deribit-powered gateway (ADR 0031).
Coinbase(public=True) supports spot market discovery, rules and tickers without
credentials. Public discovery uses the
complete default product response. A response indicating more pages, missing
completion metadata or duplicate IDs raises an error: live small-page sweeps can
omit products, so deduplication cannot guarantee completeness.
Authenticated bulk tickers combine catalogue last-trade prices and base volumes with the
best-bid/ask endpoint,
including quoted sizes. Quotes are fetched in bounded batches for the selected
products, under the caller's retry context. A missing book or empty side remains
None; request failures propagate. The two sources are separate observations,
not an atomic snapshot.
Public tickers use one public.book(limit=1) request per selected product to obtain
native bid/ask prices and sizes. Pass selected market IDs to limit request volume;
a full exchange sweep needs a book request for every product. Each request uses the
caller's retry context. Account fees, balances and trading still require credentials.
Metadata
Release files for tribulnation-coinbase 0.3.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 | |
|---|---|---|---|
| tribulnation_coinbase-0.3.0.tar.gz | 20.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tribulnation_coinbase-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.7 kB
Release files / tribulnation_coinbase-0.3.0.tar.gz
| Download URL | tribulnation_coinbase-0.3.0.tar.gz |
|---|---|
| Size | 20.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
240137a0d4b855cb940b90b46a968cabdffc8dd01c44770bc3ca78967553e18e
|
|
BLAKE2b-256 checksum How to use checksums |
68cdc4c6bf8c68458e905bc59f20f4e695dfeda2b25839dfeddb097a1dc3eb85
|
| 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 29, 2026.
Transparency logRelease files / tribulnation_coinbase-0.3.0-py3-none-any.whl
| Download URL | tribulnation_coinbase-0.3.0-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7cbf063fe9092ab6229edaa80c6b6224312456890b3318b6daaad56073005ee5
|
|
BLAKE2b-256 checksum How to use checksums |
384d4608bfc69f652a5118b65a660ef61b751df2961a7d083d29af676dc47e48
|
| 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 29, 2026.
Transparency log