LFJ API: Liquidity Book SDK, DEX API and Avalanche pool data
On 19 November 2026, LFJ's pools handled one in six Avalanche DEX trades. Its Liquidity Book SDK and DEX API cover pools, positions and vaults; this guide covers both, plus LFJ candles over REST.

The short answer. LFJ, the DEX formerly called Trader Joe, documents a DEX API at api.lfj.dev: 25 endpoints for pools, wallet positions, vaults, rewards and JOE supply, with API keys issued on request. Developers also get the open-source Liquidity Book contracts and an SDK.
According to DexPaprika data, LFJ's pools handled 9,786 of the 60,006 DEX trades indexed on Avalanche in the 24 hours to 19 November 2026, one in six.
LFJ used to be Trader Joe. The team announced the rename on 23 September 2024, traderjoexyz.com now redirects to lfj.gg, and DexPaprika's data uses the new name: its dex_name field reads "LFJ", "LFJ V2.1" and "LFJ V2.2". Searches for the Trader Joe API land on the same protocol.
Below: LFJ's developer tools, how access to its DEX API works, where LFJ trades on Avalanche, and how to pull candles for any LFJ pool over REST. Method at the end.
LFJ's developer tools: Liquidity Book and its SDK
LFJ's core product, Liquidity Book, is an open-source concentrated-liquidity AMM that trades in discrete price bins instead of Uniswap-style ticks. The contracts, the bin math and every interface are documented at developers.lfj.gg, alongside deployment addresses for Avalanche C-Chain, Arbitrum One and Monad mainnet, plus legacy V1 pools on BNB Smart Chain and Ethereum. The open-source SDK, @traderjoe-xyz/sdk-v2 on npm, wraps the contracts for JavaScript and TypeScript projects.
The LFJ DEX API: 25 endpoints at api.lfj.dev
Past the contracts, LFJ documents a REST API with a full OpenAPI specification, grouped like this:
Together that is 25 endpoints, covering up to ten chains depending on the endpoint. The Dex analytics endpoint returns daily reserves, volume and fees per chain as a time series, and the User group returns which bins a wallet holds and the fees it earned in each.
Access is by request: LFJ's docs offer a Google Form, or a Discord ticket for a faster answer. Every call carries the key in an x-lfj-api-key header. Without one, api.lfj.dev answers HTTP 401 with {"message":"No API key found in request"}, and with an invalid one, {"message":"Unauthorized"}, which is what it returned on 19 November 2026.
The API is built around pools, positions and vaults. For price candles and individual swaps on an LFJ pool, a chain-level index fills in, as the last section shows.
LFJ handled one in six Avalanche DEX trades on 19 November 2026
DexPaprika indexes LFJ on Avalanche as three entries: the legacy AMM and two Liquidity Book versions. Here is every DEX indexed on Avalanche that day, by 24 hour volume:
LFJ's three entries handled 9,786 trades, 16.3% of the chain's total, and $2,054,481 in volume. The legacy AMM alone holds 233 indexed pools, more than any other DEX on Avalanche. LFJ's busiest pool was WAVAX/USDC on Liquidity Book V2.2, with $1,666,272 across 2,627 trades.
Pharaoh V3 led Avalanche by volume with 74.3%; our Pharaoh API guide covers it.
LFJ pool candles and swaps over REST
Hourly candles for that WAVAX/USDC pool work without a key for the last 24 hours. A relative start keeps the call valid whenever you run it:
curl "https://api.dexpaprika.com/networks/avalanche/pools/0x864d4e5ee7318e97483db7eb0912e09f161516ea/ohlcv?start=-12h&interval=1h&limit=5"
That returns an array of candles, each carrying time_open, time_close, open, high, low, close and volume. Swap in the address of any other LFJ pool, on Avalanche or Arbitrum, and the shape stays the same. Pool search with dex_name=traderjoe_v2_2 (or traderjoe, traderjoe_v2_1) lists LFJ's pools by volume.
Individual swaps come from the pool's /transactions endpoint, one row per swap. That endpoint needs a Dev or Pro plan; without a key it answered HTTP 403 on 19 November.
Candles need no key. A free key from console.dexpaprika.com raises the rate and the quota and reaches further back in candle history, with current numbers on the pricing page, because they move. Free-tier data can be up to 60 seconds behind; real-time is the paid tier.
Common questions
Does LFJ have an API?
Yes: a DEX API at api.lfj.dev with 25 documented endpoints for pools, wallet positions, vaults, rewards and JOE supply. It is documented at developers.lfj.gg, together with the Liquidity Book contracts and the SDK.
Do I need an API key for LFJ?
Yes. Every endpoint takes an x-lfj-api-key header, and LFJ's docs offer a request form or a Discord ticket to get one.
Is LFJ the same as Trader Joe?
Yes. Trader Joe announced the LFJ name on 23 September 2024, and traderjoexyz.com redirects to lfj.gg. The SDK still ships under the @traderjoe-xyz npm scope.
How do I get LFJ price history (OHLCV)?
LFJ's DEX API returns current price and volume windows per pool, plus daily analytics per chain. For candles on a single pool, DexPaprika's /ohlcv endpoint works on every LFJ pool it indexes, without a key for the last 24 hours.
How much of Avalanche's DEX activity does LFJ carry?
On 19 November 2026, 16.3% of indexed trades and 6.5% of indexed volume, across its legacy AMM and both Liquidity Book versions.
How these numbers were measured
Everything above was read off a live source on 19 November 2026, except the endpoint inventory, described next.
The DEX API endpoint counts, groupings and chain lists come from the OpenAPI fragments embedded in LFJ's developer docs at developers.lfj.gg, one page per endpoint group, parsed on 23 September 2026. On 19 November the docs index (llms.txt) listed the same eight DEX API pages. The 401 responses are a direct request to api.lfj.dev on 19 November, with no header and with a made-up x-lfj-api-key.
The Avalanche table is the full GET /networks/avalanche/dexes response, fetched at 07:51 UTC on 19 November 2026. Shares are each DEX's figure divided by the sum of the table's rows, which is DexPaprika-indexed activity. The busiest pool comes from pool search with dex_name=traderjoe_v2_2 at the same time. The OHLCV call is quoted verbatim and returned HTTP 200 without a key; the transactions call returned HTTP 403.
Every figure is a 24 hour window closing on the measurement, so expect movement.
Full REST reference at docs.dexpaprika.com. There is a per-DEX page with a live feed for LFJ on Avalanche.
The same question for three other DEXes: what the Raydium API covers on Solana, where Uniswap sends you for market data, and what PancakeSwap documents on BNB Smart Chain.
Original CoinPaprika guide.