CCXT vs the Bequant API

bequant is a white-label venue of HitBTC — a Malta-based exchange running on the HitBTC engine, so its API is HitBTC-shaped.

Because it shares an API dialect with HitBTC, CCXT implements it by extending its hitbtc class. Everything in the CCXT vs the HitBTC API comparison applies here — this page covers only what is specific to bequant.

What is different

A distinct venue with its own accounts and listings, but the request/response formats are inherited from HitBTC. CCXT therefore implements it by extending its HitBTC class rather than duplicating a parser.

Credentials and markets are its own; only the API dialect is shared.

What CCXT gives you here

_{Figures verified September 2026 against CCXT v4.5.77, read from the source tree with build/comparisons-facts.cjs. Counts include everything inherited from hitbtc.}

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.bequant({'apiKey': '...', 'secret': '...'})
markets = exchange.load_markets()
ticker = exchange.fetch_ticker(list(markets)[0])

Because bequant lists a different market set from hitbtc, 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.bequant()
    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 bequant when you hold an account with Bequant specifically. Use hitbtc 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 hitbtc API keys work with bequant? No. It is a separate legal entity with separate accounts; you need keys issued by Bequant.

Does bequant support the full unified API? It inherits 65 unified capabilities from hitbtc. 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 Bequant-specific endpoints? Yes — all 111 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 hitbtc 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 HitBTC API — the full comparison
• hitbtc API reference — bequant inherits it; it has no separate reference page
• Install CCXT
• Manual
• More comparisons