# What to use instead of the dYdX v3 API

dYdX Trading halted v3 trading on 28 October 2024 and its API went with it. Where v3 order code, live perp data and the v3 history go now.

*https://cryptomarkets.tools/alternatives/dydx-v3*

## The subject

| Field | Value |
| --- | --- |
| Product | dYdX v3 API |
| Status | retired |
| Stopped serving | 2024-10-28 |
| Website | https://web.archive.org/web/20241013175221/https://trade.dydx.exchange/ |
| Category | Crypto Market Data APIs |

The REST and WebSocket API of dYdX v3, the StarkEx-based perpetuals exchange on Ethereum, with orders signed by a STARK key and requests by an API key, secret and passphrase.

## Replacements

*Ordered by how much of the original’s job each one covers, closest first. Paid placement does not affect this order.*

1. [dYdX v4 Clients](https://cryptomarkets.tools/tools/dydx-v4-clients.md) — The successor's official clients, for the same BTC-USD-style markets on dYdX Chain. Orders become chain transactions; no v3 key or call carries over.
2. [Hummingbot](https://cryptomarkets.tools/tools/hummingbot.md) — If the v3 code was a Hummingbot strategy, its dydx_perpetual connector was removed in September 2024 and dydx_v4_perpetual runs the same bot on v4.
3. [CCXT](https://cryptomarkets.tools/tools/ccxt.md) — Its dydx class, added in November 2025, speaks the v4 indexer, and the same unified methods reach the other perp venues on this page.
4. [Hyperliquid Python SDK](https://cryptomarkets.tools/tools/hyperliquid-python-sdk.md) — Another on-chain perp order book with hourly funding and an official client, where an agent key can trade but cannot withdraw.
5. [Aster Market Data API](https://cryptomarkets.tools/tools/aster-api.md) — Keyless perp books, candles, funding and liquidations from a DEX, in Binance's shapes, for code that only ever read v3's public endpoints.
6. [Tardis.dev](https://cryptomarkets.tools/tools/tardis-dev.md) — The v3 tape itself, kept as a delisted feed. Trades, L2 books, quotes and funding snapshots for 38 markets, 6 April 2021 to 30 October 2024.

## The product

dYdX v3 was a perpetual-futures exchange built on StarkEx, StarkWare's layer-2 system for
Ethereum. Funds and settlement sat in an Ethereum smart contract governed by tokenholders; the
matching engine was offshore and run by dYdX Trading Inc., which collected the trading fees. Its
own July 2024 post describes it in exactly those terms. Collateral was USDC, every market was a
perpetual quoted in USDC under names such as BTC-USD and ETH-USD, and funding was paid every hour.

The API was the exchange's front door for anyone automating. Public endpoints for markets, order
books, trades, candles and historical funding needed no key. Private ones needed two layers of
credentials derived from an Ethereum signature at onboarding: an API key, secret and passphrase
to sign each request, and a STARK key pair to sign every order and withdrawal. dYdX published
official Python and TypeScript clients for it, `dydx-v3-python` and `v3-client`.

**The end came in one notice, on dYdX Trading's blog.** On 23 July 2024 the company said it was
"exploring strategic alternatives" for the v3 technology because it was "all in on dYdX Chain".
On 27 September 2024 it announced the sunset:

> All trading, oracle-price updates, and funding payments are planned to halt on October 28th at
> 12:05 P.M. UTC.

The same notice said that two days later, on 30 October, the Ethereum contract would register the
exchange as frozen, after which users could withdraw the full USDC value of their accounts, open
positions valued at the oracle prices at the halt. It said that "dYdX Trading plans to host
read-only historical data via API for at least 1 year after the shut-down date", and that the
change "only affects users of dYdX v3" — dYdX Chain and the v4 API were untouched. The dYdX
Foundation's governance FAQ, published the same day, says the same.

Tardis.dev's v3 feed stops on 30 October 2024. The read-only API outlived the exchange for about
the year promised: the Wayback Machine captured a 200 from its markets endpoint on 1 August 2025,
and our own request on 27 October 2026 got a 503. We found no notice dating the end of the
read-only service.

## What to use instead

Nobody replaces v3 whole, and the successor is not a new version of the same API. What you held
was one of three things: order code against the v3 private API, a reader of its public market
data, or a history. Each goes somewhere different.

**If you traded on v3 and want to stay with dYdX,** the
[dYdX v4 Clients](https://cryptomarkets.tools/tools/dydx-v4-clients) are the official way onto dYdX Chain, in TypeScript,
Python, Rust and C++. The market names look the same and nothing else is. On v4 an order is a
transaction signed by the account's wallet key and broadcast to a validator, while reads come from
a separately hosted indexer, so the client layer is a rewrite rather than a base-URL change. If
your v3 code was a [Hummingbot](https://cryptomarkets.tools/tools/hummingbot) strategy, Hummingbot deleted its v3
`dydx_perpetual` connector on 17 September 2024 and maintains `dydx_v4_perpetual`; the strategy
survives and the connector config changes.

**If you want order code that is not tied to one venue again,** [CCXT](https://cryptomarkets.tools/tools/ccxt) added a
`dydx` class in November 2025, a year after v3 closed, and it speaks the v4 indexer. The same
unified methods then reach Hyperliquid, Aster and the other perpetual venues it carries. For
another single-venue client with the same shape of trade-off as v3's own, the
[Hyperliquid Python SDK](https://cryptomarkets.tools/tools/hyperliquid-python-sdk) is the official client for the other large
on-chain order book, and its agent key can trade but cannot withdraw.

**If you only read v3's public endpoints,** the [Aster Market Data API](https://cryptomarkets.tools/tools/aster-api) serves
books, candles in last, index and mark flavours, funding history and liquidation streams from a
perp DEX with no key, on Binance's paths and response shapes. The cross-venue view is on
[how to get funding and open interest](https://cryptomarkets.tools/how-to/get-funding-and-open-interest).

**If what you needed was the history,** [Tardis.dev](https://cryptomarkets.tools/tools/tardis-dev) recorded the v3 WebSocket
feed and keeps it as a delisted exchange: 38 markets, trades, incremental L2 books, quotes and
derivative-ticker snapshots, from 6 April 2021 to 30 October 2024. The first day of each month
downloads free without a key, which is enough to check that the files fit your code before paying.
[CoinAPI](https://cryptomarkets.tools/tools/coinapi) still lists dYdX V3 among its DEX venues, but its card dates DEX trade
history from 22 November 2023 at the earliest, and we could not confirm the v3 range without a
key. [Coin Metrics](https://cryptomarkets.tools/tools/coin-metrics) carries a `dydx` exchange whose trades start on 13 March
2025: that is v4, and none of it is v3.

## What you give up

**The history behind the same API.** On v3 the endpoint that served today's funding also served
every hourly funding rate since launch. The v4 indexer starts with dYdX Chain, the read-only v3
API now answers 503, and the only v3 series left on this page is a vendor's recording of the
WebSocket feed. Funding in Tardis's files is a snapshot of what the feed published, not the
settled-rate table `/v3/historical-funding` returned, so a backtest that needs exact payments
from 2021 to 2024 is rebuilding them.

**One continuous venue.** v3 and v4 share a brand, a token and ticker strings, and they are two
order books with different liquidity, different fee schedules and different participants. A
BTC-USD series that runs from 2021 to today is two venues glued at October 2024, whether or not the
chart shows a seam.

**API-key trading.** v3 let a bot hold an API key, secret and passphrase plus a STARK key, all
derived once from an Ethereum signature. On v4 the signing key is the chain account's own key.
Nothing on this page reproduces v3's split between a request-signing credential and an order-
signing one, and the agent key on Hyperliquid is the nearest equivalent rather than the same thing.

## Migration notes

**Same tickers, different markets.** v3 and v4 both call the bitcoin perpetual `BTC-USD`. Any
table keyed on the ticker alone will join the two venues without complaint. Key history on venue
and ticker together, and treat 28 October 2024 as the end of one series rather than a gap in it.

**Timestamps change type.** v3 returned ISO 8601 strings such as `2021-04-09T21:08:34.984Z`.
Aster's Binance-shaped responses and Hyperliquid's API count in epoch milliseconds. A parser that
quietly falls back on a string comparison will sort fine and filter wrongly.

**Candles were coarse and capped.** v3's candle endpoint returned at most 100 per request, and the
docs described the period as 1HOUR or 1DAY in one place while listing resolutions down to 1MIN in
another. If your v3 job paged candles, its page size and its resolution names are both wrong
everywhere else.

**Rate limits were per IP, and still are.** v3 allowed 175 GETs per 10 seconds per IP and, on the
WebSocket, two subscriptions a second per connection. Aster counts request weight per IP rather
than calls, so the same polling loop can land in a 429 and then a ban. Read the new venue's limits
before reusing the loop.

**Expect a crossed book now and then in the archive.** Tardis notes that rebuilding the v3 book
from dYdX's WebSocket updates occasionally gives best bid at or above best ask, a known
exchange-side issue. Filter those minutes before computing spreads or queue positions.

**Withdraw, then delete the keys.** The notice says USDC left in the v3 contract stays withdrawable
indefinitely, through the Ethereum contract rather than through dYdX. Withdrawing needs the
Ethereum key that onboarded the account; once the USDC is out, take that key off the bot host.
[What your API key lets a bot do](https://cryptomarkets.tools/guides/what-your-api-key-lets-a-bot-do) covers the replacement,
and [what happens to data after a delisting](https://cryptomarkets.tools/guides/what-happens-to-data-after-a-delisting) covers
why nobody keeps your own fills for you.

## FAQ

### When exactly did the dYdX v3 API stop working?

dYdX Trading's notice of 27 September 2024, v3 Product Sunset, set the halt of all trading, oracle-price updates and funding payments for 12:05 UTC on 28 October 2024, and said the Ethereum contract would register the exchange as frozen on 30 October. It promised read-only historical data via the API for at least a year after the shutdown; on 27 October 2026 the API host answered 503.

### Was dYdX v4 affected?

No. The same notice says the change only affects users of dYdX v3, and that users of dYdX Chain, dydx.trade or the v4 API are unaffected. The dYdX Foundation's governance FAQ of the same day repeats it.

### Can I still withdraw funds from dYdX v3?

By dYdX Trading's notice, yes. Balances, including open positions valued at the oracle prices when trading halted, stay withdrawable from the Ethereum smart contract indefinitely. It said that once its own interface wound down, withdrawals would be supported by L2BEAT, an independent third party.

### Is dYdX v3 historical data still available anywhere?

Tardis.dev keeps it as a delisted feed, with trades, order books, quotes and funding snapshots from 6 April 2021 to 30 October 2024. The v4 indexer does not serve v3 history, and Coin Metrics' dYdX markets start in March 2025, so they are v4 only.