CCXT vs the Foxbit API and the official Foxbit SDK

Foxbit is a Brazilian exchange, and the BRL pairs are the point: BTC/BRL, ETH/BRL, USDT/BRL and a long tail beside them. Its REST v3 API is signed with an HMAC over the timestamp, method, path, query string and body.

Two ways to integrate: the official SDK, @foxbit-group/rest-api, which Foxbit recommends for new projects and which is available for JavaScript and TypeScript; or CCXT, which speaks the same REST v3 API behind the interface it uses for 103 other venues.

The question that decides it: are you writing JavaScript, and is Foxbit your only venue?

TL;DR

• Pick the official SDK if you are in JavaScript or TypeScript, Foxbit is your only venue, and you want typed models that match Foxbit's own API surface one-for-one.
• Pick CCXT if you want unified symbols and structures, seven languages, a built-in rate limiter and typed errors — the same code shape you already use for Binance or Kraken.
• Neither side streams. CCXT implements no watch* methods for Foxbit, and the official SDK is REST-only — its name says so. Foxbit's WebSocket v2 has one sample, in JavaScript, in the samples repository. If you need live streams from Foxbit, that is a hand-written integration either way.

At a glance

_{Figures verified September 2026 against CCXT v4.5.77, the foxbit-group/foxbit-api-samples repository and its SDK and raw-REST examples, the @foxbit-group/rest-api npm registry metadata, live responses from api.foxbit.com.br, and install counts from npm and PyPI.}

The same job, written both ways

Fetch a ticker

import ccxt

exchange = ccxt.foxbit()
ticker = exchange.fetch_ticker('BTC/BRL')
print(ticker['last'], ticker['baseVolume'], ticker['quoteVolume'])

Foxbit's ticker nests the interesting fields: last_trade.price, rolling_24h.open/high/low/volume/quote_volume, best.ask.price and best.bid.price. CCXT flattens that into a unified ticker structure — last, open, high, low, bid, ask, baseVolume, quoteVolume, percentage, timestamp in milliseconds — the same keys and units as every other exchange, and the symbol is 'BTC/BRL' rather than btcbrl.

Place a limit order

import ccxt

exchange = ccxt.foxbit({'apiKey': '...', 'secret': '...'})
order = exchange.create_order('BTC/BRL', 'limit', 'buy', 0.0001, 500000)
print(order['id'], order['status'])
exchange.cancel_order(order['id'], 'BTC/BRL')

Both are readable, and both sign for you. The difference is portability, not verbosity: the SDK's market_symbol, side: 'BUY' and string quantity are Foxbit's own field names, so moving the strategy to a second venue means a second vocabulary. CCXT returns a unified order structure, and the same create_order call works on 103 other exchanges.

If you write it yourself instead, the signing is:

const preHash = `${timestamp}${method}${path}${queryString}${rawBody}`;
const signature = CryptoJS.HmacSHA256(preHash, process.env.FOXBIT_API_SECRET).toString();
// sent as X-FB-ACCESS-KEY, X-FB-ACCESS-TIMESTAMP, X-FB-ACCESS-SIGNATURE

CCXT builds that string and those headers internally, including the awkward part — the query string has to be reconstructed in the exact order it was sent.

Where the differences actually bite

Seven languages, not two

This is the biggest practical difference. Foxbit's samples repository has raw REST v3 examples in twelve languages, but the official SDK is JavaScript and TypeScript only. If your service is Python, Go, C#, PHP or Java, the SDK is not available to you and the samples are starting points you finish yourself.

CCXT is written once in TypeScript and transpiled to JavaScript, Python, PHP, C#/.NET, Go and Java, with identical method names and return structures.

import ccxt from 'ccxt';
const exchange = new ccxt.foxbit ();
const ticker = await exchange.fetchTicker ('BTC/BRL');

BRL alongside everything else

A Brazilian desk usually runs BRL pairs on a local venue and quotes against a global one. In CCXT that is a loop, not two integrations:

import ccxt

foxbit = ccxt.foxbit()
binance = ccxt.binance()
local = foxbit.fetch_ticker('BTC/BRL')['last']
offshore = binance.fetch_ticker('BTC/USDT')['last']
print(local, offshore)

Both tickers are the same structure, so the spread calculation does not care which venue produced which number.

Rate limits you do not have to model

CCXT's Foxbit definition sets rateLimit to 33.334 ms — 30 requests per second, expressed as milliseconds per request — with per-endpoint weights, and the throttler is on by default (enableRateLimit = true). You call methods in a loop; the library paces them.

Precision and string math

Foxbit publishes per-market price and quantity precision, and BRL prices run to six figures where the quantity runs to eight decimal places — exactly the range where float rounding starts producing rejected orders. CCXT loads the metadata with the markets and rounds through the Precise string-arithmetic class:

amount = exchange.amount_to_precision('BTC/BRL', 0.000123456789)
price = exchange.price_to_precision('BTC/BRL', 396217.123456)

One error hierarchy

CCXT maps Foxbit's error responses onto its typed exception tree — InsufficientFunds, InvalidOrder, OrderNotFound, AuthenticationError, RateLimitExceeded, NetworkError and 35 more, all descending from BaseError. You write except ccxt.InsufficientFunds once and it keeps working on the next exchange.

Account plumbing is unified too

Beyond trading, the venue's unified capabilities include fetchBalance, fetchLedger, fetchMyTrades, fetchOrders, fetchOpenOrders, fetchClosedOrders, fetchCanceledOrders, fetchDepositAddress, fetchDeposits, fetchWithdrawals, fetchTransactions, fetchTradingFees and fetchCurrencies — 37 unified capabilities in total, 24 of them fetch* methods.

Nothing is hidden — the implicit API

Alongside the unified methods, all 22 Foxbit endpoints are generated as callable implicit methods, with signing, rate limiting and error mapping applied:

response = exchange.v3_public_get_markets()

Browse them on the Foxbit implicit API page.

What the official Foxbit SDK does better

Real advantages, not padding:

• Typed models that match Foxbit's API exactly. Full TypeScript typing, built-in parameter validation and automatic error handling, against Foxbit's own request and response shapes. When you are reading Foxbit's reference while debugging, that is one hop instead of two.
• Twelve languages of raw samples. The foxbit-api-samples repository has REST v3 examples in JavaScript, TypeScript, Go, Python, Ruby, PHP, C#, Java, C++, Dart, Kotlin and Swift. Dart, Kotlin, Swift, Ruby and C++ are outside CCXT's seven languages entirely — if you are writing a Flutter or iOS app, that is where you start.
• The WebSocket v2 sample. Foxbit's samples repository has a JavaScript WebSocket example. CCXT has no streaming support for Foxbit at all, so live data means the raw socket regardless.
• New endpoints on day one. Whatever Foxbit ships appears in their own SDK and samples first; a unified CCXT method may follow later, though the implicit API closes most of that gap immediately.
• A much smaller install. For a Foxbit-only Node service, @foxbit-group/rest-api is a fraction of the size of all of CCXT.

If you are building a Foxbit-only application in JavaScript or TypeScript, the official SDK is the better fit — and if you need Foxbit's live feed, you will be writing WebSocket code yourself either way.

Migrating from the Foxbit SDK to CCXT

Start with Install, then the Manual, then the foxbit unified API reference.

FAQ

Does Foxbit have an official Python SDK? No. The official SDK, @foxbit-group/rest-api, is published for JavaScript and TypeScript. Foxbit's samples repository has raw REST v3 examples in Python and eleven other languages, but they are examples rather than a maintained package. For Python, Go, C#, PHP or Java, CCXT is the maintained option.

Does CCXT support Foxbit WebSockets? No. CCXT implements zero watch* methods for Foxbit, so streaming is not available through CCXT for this venue. Foxbit documents a WebSocket v2 API and ships one JavaScript sample for it.

Does CCXT support Foxbit's BRL pairs? Yes — Foxbit is a spot venue and its BRL markets load as ordinary unified symbols: 'BTC/BRL', 'ETH/BRL', 'USDT/BRL' and the rest, alongside 'BTC/USDT'.

Does Foxbit have a sandbox CCXT can use? setSandboxMode is not available for this venue in CCXT — no test URLs are declared. Test with small live orders, or against static fixtures.

Can I still call Foxbit-specific endpoints from CCXT? Yes — all 22 of them, as implicit methods, with signing and rate limiting applied.

Is CCXT free? Yes. MIT-licensed, no paid tier.

Next steps

• Install CCXT in your language
• Manual — the unified API, structures and conventions
• foxbit unified API reference
• foxbit implicit API — every raw endpoint
• More comparisons