Crypto Exchange API Change Tracker

If you run an arbitrage strategy, a market-making bot, or any automated execution across multiple venues, a silent API change is one of the most expensive things that can happen to you. An exchange deprecates an endpoint, renames a field, tightens a rate limit, or bumps a version, and suddenly your orders fail, your fills go stale, or your risk logic reads the wrong number. The exchange published a changelog. You just did not see it in time.

This tracker solves that. Every day it checks the official API documentation and changelog page of each exchange that SharpTrader connects to, and flags anything that changed since the previous day. Use it as an early warning system for your own integrations, or just to keep a pulse on how fast each venue moves.

Live tracker

Rows are colour coded by what happened on the most recent daily check:

Every exchange we monitor, with its official changelog

The 27 venues below are the crypto exchanges SharpTrader integrates with over API. Bookmark the changelog links: these are the canonical pages each exchange uses to announce API changes, deprecations, and new versions.

Why exchange API changes break trading bots

Automated strategies assume the venue behaves the way it did yesterday. When that assumption quietly breaks, the failure mode is rarely a clean error. It is a wrong number that flows straight into your order logic. Here is where it bites hardest.

Catching these on day one, rather than during a live incident, is the entire point of watching changelogs. For deeper background on the strategies affected, see our guides to crypto arbitrage, crypto arbitrage bots, and latency arbitrage.

How the tracker works

Once per day, an automated job fetches each exchange’s changelog or API documentation page, strips out volatile markup such as scripts and per-request tokens, and fingerprints the meaningful content. It compares that fingerprint to the previous day. If it differs, the exchange changed something worth reading, and the row turns red. If a page cannot be reached, for example when a venue blocks automated requests, the row turns amber so you know the check was inconclusive rather than clean.

The highest confidence signals come from exchanges that publish a dedicated changelog file, such as Binance, Kraken, KuCoin, MEXC, OKX, Poloniex, Bybit, BitMEX, HitBTC, Bitfinex, and Bitbank. Venues that ship single page documentation are still tracked and act as a useful tripwire.

FAQ