CCXT vs the Bybit EU API
Bybit EU is a regional entity of Bybit. What CCXT's bybiteu class covers, how it differs from bybit, and where the full comparison lives.
bybiteu is a regional entity of Bybit — the MiCA-regulated European entity of Bybit, serving EEA users from a separate host.
Because it shares an API dialect with Bybit, CCXT implements it by extending its bybit class. Everything in the CCXT vs the Bybit API comparison applies here — this page covers only what is specific to bybiteu.
What is different
Separate registration and separate API host from bybit.com. Product coverage is narrower than the global venue, reflecting what the European entity is licensed to offer.
Credentials are not shared with the global
bybitclass.
What CCXT gives you here
bybiteu | |
|---|---|
| Unified capabilities | 123 (inherited from bybit plus its own overrides) |
fetch* methods | 61 |
WebSocket watch* methods | 25 |
| Raw endpoints as implicit methods | 404 |
Testnet via setSandboxMode | yes |
| Languages | TypeScript, JavaScript, Python, PHP, C#/.NET, Go, Java |
| Licence | MIT |
Figures verified September 2026 against CCXT v4.5.77, read from the source tree with build/comparisons-facts.cjs. Counts include everything inherited from bybit.
Using it
The class name is the only thing that changes — every unified method behaves as it does everywhere else in CCXT:
import ccxt
exchange = ccxt.bybiteu({'apiKey': '...', 'secret': '...'})
markets = exchange.load_markets()
ticker = exchange.fetch_ticker(list(markets)[0])Because bybiteu lists a different market set from bybit, call load_markets() and pick symbols from it rather than assuming a pair exists.
Streaming works the same way:
import ccxt.pro, asyncio
async def main():
exchange = ccxt.pro.bybiteu()
while True:
orderbook = await exchange.watch_order_book('BTC/USDT')
print(orderbook['bids'][0], orderbook['asks'][0])
asyncio.run(main())Should you use this class or the parent?
Use bybiteu when you hold an account with Bybit EU specifically. Use bybit when you hold an account with the global venue. They are different venues with separate credentials, so this is not a preference — it follows from where your account is.
FAQ
Do my bybit API keys work with bybiteu?
No. It is a separate legal entity with separate accounts; you need keys issued by Bybit EU.
Does bybiteu support the full unified API?
It inherits 123 unified capabilities from bybit. Where the venue does not offer a feature, the corresponding has flag is turned off, and the method raises NotSupported rather than failing quietly. Check exchange.has at runtime.
Can I reach Bybit EU-specific endpoints?
Yes — all 404 endpoints in this class's api block are generated as implicit methods, with signing, rate limiting and error mapping applied. The mechanism is documented on the bybit implicit API page; this venue's own endpoint list differs slightly from the parent's.
Is CCXT free? Yes. MIT-licensed, including the WebSocket support.
Next steps
- CCXT vs the Bybit API — the full comparison
bybitAPI reference —bybiteuinherits it; it has no separate reference page- Install CCXT
- Manual
- More comparisons
CCXT vs the Binance.US API
Binance.US is a regional entity of Binance. What CCXT's binanceus class covers, how it differs from binance, and where the full comparison lives.
CCXT vs the FMFW.io API
FMFW.io is a white-label venue of HitBTC. What CCXT's fmfwio class covers, how it differs from hitbtc, and where the full comparison lives.