Bybit SDK
Tribulnation SDK implementation for Bybit.
Installation
pip install tribulnation-bybit
Surfaces
| Surface | Class | Credentials |
|---|---|---|
| Market | tribulnation.bybit.BybitMarket |
keyed (pass public=True for market data only) |
| Earn | tribulnation.bybit.Earn |
keyed, though every catalogue endpoint is public |
| Wallet | tribulnation.bybit.Wallet |
keyed |
| Report | tribulnation.bybit.Report |
keyed |
from tribulnation.bybit import BybitMarket
async with BybitMarket.new() as venue:
perp = await venue.perp_exchange('perp')
market = await perp.market('BTCUSDT')
print(await market.next_funding())
Credentials come from BYBIT_API_KEY/BYBIT_API_SECRET when not passed.
Exchanges
Bybit v5 is one API discriminated by a category parameter rather than separate spot and
futures endpoints, so spot and perp share a single connection, instrument cache and
private stream.
perp lists linear perpetuals only. Bybit's linear category also carries 40-odd dated
futures, which settle on a delivery date and pay no funding — nothing about the
PerpMarket contract describes them.
Regions
Bybit's regional entities are separate accounts with separate keys, separate environment
variables and different product universes; bybit.eu in particular lists no derivatives
at all. Pick one at construction:
BybitMarket.new(region='eu') # reads BYBIT_EU_API_KEY / BYBIT_EU_API_SECRET
History windows
Bybit caps how wide a single history query may be and rejects a wider one rather than
truncating it — 7 days for trade history and the transaction log, 30 for deposit and
withdrawal records — and refuses any window starting more than two years back. Both
Market.trades_history() and Report.history() take whatever window you give them and
split it to fit; Report.history() with no window sweeps the full two years.
Funding payment signs
Since 0.5.0, funding payments are positive when received and negative when paid, for every supported history scope. Requires SDK >=2.10.0. Funding rates keep their existing signs. See migration notes before upgrading.
Metadata
Release files for tribulnation-bybit 0.7.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_bybit-0.7.0.tar.gz | 25.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tribulnation_bybit-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.2 kB
Release files / tribulnation_bybit-0.7.0.tar.gz
| Download URL | tribulnation_bybit-0.7.0.tar.gz |
|---|---|
| Size | 25.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc317e6e549c765a7a82babe7818831df8a82f18d8b6bbd2baa21a4ccfbc7891
|
|
BLAKE2b-256 checksum How to use checksums |
18751ae24f2c21651a6ea01c517b9d80ae76705dc93d43a7f595254afa3b9664
|
| 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 Oct 9, 2026.
Transparency logRelease files / tribulnation_bybit-0.7.0-py3-none-any.whl
| Download URL | tribulnation_bybit-0.7.0-py3-none-any.whl |
|---|---|
| Size | 36.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0c6073f6a37b507989ab327f6053fb4faaae611da43f3cc77e80e40cd61e8d9
|
|
BLAKE2b-256 checksum How to use checksums |
aa4948b2690929d9ed6da905b92dc0c5714212d16305cc2991bfa6248d0b648c
|
| 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 Oct 9, 2026.
Transparency log