How far back each exchange's API actually lets you go (11 exchanges compared)

Calix — Sun, 25 Oct 2026 07:40:00 +0000

I build a read-only crypto portfolio tracker, which means I spend a lot of time asking exchange APIs for old trades and finding out how little they will give me. We integrate 11 exchanges, and I keep one manifest of how far back each one will actually serve history. This post is that manifest, with the endpoints behind it.

The short version: two different limits get confused, and only one of them is a problem.

Window caps versus retention walls

A window cap limits how much time a single request may span. HTX's match results accept at most a 48 hour span. Bybit's execution list works in 7 day windows. Gate.io allows 30 days, Bitget 90, Upbit 7. These are annoying, but they are not limits on your history. You loop backwards in chunks and eventually reach the start of the account. If your tool says "only 7 days available" because of a window cap, the tool is lazy, not the exchange.

A retention wall means the data no longer exists behind the API. Nothing you write can recover it. OKX serves about 90 days of fills. MEXC serves about a month. Bitget about 90 days. HTX about 120. A wall is a fact about the exchange, and it decides how much of your cost basis can be rebuilt from an API key.

Conflating the two would put a warning on six venues about caps we walk through without trouble, so the manifest deliberately lists only walls. Splitting them is the most useful thing in it.

One more distinction that bit me: the same venue can have a wall on one surface and none on another. OKX serves its funding ledger (deposits, withdrawals, fiat, rewards) back to February 2021, while its savings interest is a rolling 30 days. A year-old month shows real deposits next to a confident zero of earnings.

The table

Numbers come from the manifest in our repo (packages/ui/src/history-limits.ts), which a test keeps in sync with the adapter registry, so a new venue cannot ship without declaring its limits. "Full" means no retention wall: the API reaches account opening. "About" is on purpose; exchanges do not promise these figures, and I would rather round than imply a contract.

Exchange	Trade history	Deposits / withdrawals	Endpoints and quirks
Binance	Full	Full	`/api/v3/myTrades` requires a symbol, so there is no account-wide trade feed: you have to know which pairs to ask about. A coin bought and fully sold, with no deposit or withdrawal pointing at it, is named only by the daily account snapshot (`/sapi/v1/accountSnapshot`), which reaches about 30 days back. Transfers (`/sapi/v1/capital/deposit/hisrec`, `withdraw/history`) walk in 90 day windows back to account opening.
OKX	About 90 days	Full (funding bills back to Feb 2021)	`/api/v5/trade/fills-history` serves roughly 3 months. A deeper `/api/v5/trade/fills-archive` exists but needs a separately requested download, and returned 404 for the account shape I tested. Savings interest on `/api/v5/finance/savings/lending-history` is a rolling 30 days.
KuCoin	Full	Full	Per-fill data (`/api/v1/fills`) is only 7 days, but done orders (`/api/v1/orders`, status done) reach account opening with a 7 day range cap per query, so trades are reconstructed from orders. `/api/v1/accounts/ledgers` is capped at 1 year with a 24 hour query window.
Gate.io	Full	Full	`/spot/my_trades` and `/wallet/deposits` use a 30 day request window, walked back in full.
Bybit	About 2 years	Full	`/v5/execution/list` retains roughly two years of executions and is queried in 7 day windows. Older fills come back empty rather than as an error.
Coinbase	Full	Full	Advanced Trade fills (`/api/v3/brokerage/orders/historical/fills`) are cursor paginated with no retention floor. Simple-mode buys and sells are not in that feed at all; they live on the legacy v2 `/v2/accounts/{id}/buys` and `/sells` endpoints, which Coinbase has deprecated but still serves, with the real fiat amount.
Kraken	Full	Full	`/0/private/TradesHistory` is account-wide, and `/0/private/Ledgers` carries the movements. Both reach the start.
Bitget	About 90 days	Full	`/api/v2/spot/trade/fills` has a 90 day wall. Deposit and withdrawal records (`/api/v2/spot/wallet/deposit-records`) walk 90 day windows back to the 2018 launch.
Upbit	Full	Full	`/v1/orders/closed` is queryable 7 days at a time; you walk back about 11 years. Markets are KRW based.
MEXC	About a month (31 days)	About 90 days	`/api/v3/myTrades` plus 7 day windows inside a hard retention limit. Older data is only available as a manual export from the website.
HTX	About 120 days	About a year	`/v1/order/matchresults` caps each query at 48 hours and returns at most 500 rows per page, so a busy window has to be split. Transfers come from `/v1/query/deposit-withdraw`.

Five of the eleven have a trade wall: OKX, Bybit, Bitget, MEXC and HTX. MEXC and HTX also wall transfers. For KuCoin the honest summary is "full history", even though one of its endpoints is walled at 7 days; I document the outcome, not the endpoint.

A note on sourcing. The OKX figures were verified against a real account in September 2026, and the KuCoin ones were re-checked against KuCoin's own docs in August 2026. The rest are the limits recorded in each adapter from earlier probing, and I did not re-probe all of them for this post. Re-probe before you build on any of it. Exchanges change these quietly.

Why this matters at year end

This is the part that made me write the post. Walls are measured from today, not from the start of the year. If you read the API in the last week of October 2026, the reach is roughly:

OKX and Bitget, 90 days: back to late July
HTX, 120 days: back to late June
MEXC, about a month: back to late September
Bybit, about 2 years: back to late October 2024

By 31 December the same walls reach back only to about 2 October (OKX, Bitget), 2 September (HTX) and 30 November (MEXC). Anything you traded earlier in 2026 on those venues will be gone from the API by then. It is not hidden, it is deleted from the API's point of view. Bybit's two year wall means 2024 trades are the ones leaving now.

The consequence is not abstract. On one real OKX account, 90 days of fills against an account funded since March 2024 left about 27 months of buys unrecorded. It surfaced as "you hold 87 LINK the ledger has never seen". A tool built on such an API will quietly compute a cost basis that is wrong forever, and the symptom does not tell you whose fault it is.

What to do about it now

Export CSVs from each exchange's web UI before the wall moves. Trade history and deposit/withdrawal history, the longest range each site allows. For MEXC, this is the only route to anything older than the API serves. Do the venues with the shortest walls first: MEXC, then OKX, Bitget, HTX.
Do it per account and per product. Spot, funding, earn and derivatives are separate ledgers. OKX derivatives bills, for instance, are 7 days live and 3 months archived.
Store the files somewhere you control. An export is the only copy you will ever have of the data the API has already dropped.
If you build against these APIs, record the first sync date. A history that starts at your first successful sync is a different claim from a history that starts at account opening, and your users will want to know which one they have.
Do not let a lazy walk truncate you. Never stop a backward window walk after N empty windows. Real accounts have long gaps, and you will silently lose everything older.

None of this is tax advice. It is just arithmetic about which dates are still reachable.

If you only want to see how an allocation would have held up, rather than rebuild old trades, the free in-browser stress test needs none of this history: whereitgoes.money/stress-test.

The per-exchange breakdown I maintain for users is on whereitgoes.money/exchanges.

I build WhereItGoes; this article was drafted with AI assistance and checked against the code.

DEV Community: Calix

How far back each exchange's API actually lets you go (11 exchanges compared)

Window caps versus retention walls

The table

Why this matters at year end

What to do about it now