CCXT vs the Binance COIN-M Futures API

binancecoinm is a product line of Binance — Binance's coin-margined futures, where the contract is collateralised in the base asset rather than in USDT.

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

What is different

Same exchange and credentials as binance, different product line and host. The equivalent of ccxt.binance({"options": {"defaultType": "delivery"}}).

Inverse contracts: margin, PnL and position size are denominated in the base coin, so notional maths differs from the USD-M class. Symbols look like BTC/USD:BTC.

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 binance.}

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

Because binancecoinm lists a different market set from binance, 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.binancecoinm()
    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 binancecoinm when you hold an account with Binance COIN-M Futures specifically. Use binance when you hold an account with the main venue and want its other product lines from one client. They are different hosts, so this is not a preference — it follows from where your account is.

FAQ

Do my binance API keys work with binancecoinm? Yes — it is the same account and the same credentials, just a different product host.

Does binancecoinm support the full unified API? It inherits 153 unified capabilities from binance. 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 Binance COIN-M Futures-specific endpoints? Yes — all 808 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 binance 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 Binance API — the full comparison
• binance API reference — binancecoinm inherits it; it has no separate reference page
• Install CCXT
• Manual
• More comparisons