Get token price history and OHLCV data

Get historical crypto price data (OHLCV) for any token across 36 blockchains. Perfect for building charts, backtesting strategies, and price analysis.

Tutorial overview

Pull historical OHLCV from a pool using start, limit, and interval, with tips for smoothing and inverted ratios.

Having trouble with the API? We’re here to help - drop us a line and we’ll get you sorted.

Why you need historical price data?

Building a crypto app? You’ll likely need price charts, volatility analysis, or backtesting data. That’s where OHLCV (Open, High, Low, Close, Volume) data comes in - it’s the backbone of any serious crypto application.

Common use cases:

• Price charts in trading apps
• Backtesting trading strategies
• Volatility analysis for risk management
• Historical performance dashboards
• Market research and analytics

Quick Start: If you know your token already, jump to Step 2 to grab the data immediately.

---

Step 1: Find your token’s trading pool

Here’s the thing - on this endpoint historical data comes from one trading pool, not from the token as a whole. This makes sense because prices happen where people trade.

On a Dev or Pro plan you can skip this step. Token OHLCV returns USD candles for the token aggregated across every pool it trades in, so there is no pool to pick.

Quick search (recommended)

The fastest way to find what you need using the Search API:

curl "https://api.dexpaprika.com/search?query=USDC" | jq

Pro tip: Search returns tokens, pools, and exchanges. Look for pools with high volume - they’ll have the most reliable price data.

If you have the token address

Skip the search and go straight to pools using pool search with the token_address filter:

curl "https://api.dexpaprika.com/networks/ethereum/pools/search?token_address=0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48" | jq

The token_address filter only works on the per-network /networks/{network}/pools/search. The cross-network /pools/search accepts the parameter but silently ignores it.

Always pick pools with decent volume (>$10k daily). Low-volume pools can have weird price spikes that don’t reflect real market conditions.

---

Step 2: Get price history data

Now for the good stuff. Here’s how to pull historical OHLCV data using the Pool OHLCV API:

# Hourly candles for the last 24 hours, no key needed
curl "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/ohlcv?start=-24h&limit=24&interval=1h&inversed=true" | jq

How far back you can go and how fine the candles can be depends on your plan. Without a key you get 1h and up over the last 24 hours, which start=-24h selects. A free key opens 7 days at 10m and longer, Dev 30 days at every interval, and Pro everything. The full table is in OHLCV limits by plan.

With a free key, send it as the Authorization header on its own:

# Hourly candles for the last 7 days, free key
curl -H "Authorization: $DEXPAPRIKA_API_KEY" "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/ohlcv?start=-7d&limit=168&interval=1h&inversed=true" | jq

(Using USDC/ETH pool on Ethereum as example in this tutorial)

What these parameters do:

Parameter	What It Does	Example
start	When to start collecting data, inside your plan’s history window	-24h (relative to now), Unix timestamp, RFC 3339 or YYYY-MM-DD
limit	How many data points (max 1000)	24 for a day of hourly candles
interval	Time between each point	1h, 6h, 24h without a key; 10m and longer with a free key
end	When to stop (optional), inside the same window	-1h (relative to now), Unix timestamp, RFC 3339 or YYYY-MM-DD
inversed	Flip the price ratio	true for ETH/USDC → USDC/ETH

What you get back:

[
  {
    "time_open": "2025-01-30T00:00:00Z",
    "time_close": "2025-01-31T00:00:00Z",
    "open": 3115.1614508315265,
    "high": 3277.717757396331,
    "low": 3097.803416632386,
    "close": 3250.184016286268,
    "volume": 226403988
  }
]

Each data point gives you everything you need for candlestick charts or analysis.

---

Time intervals that actually matter

Choose based on what you’re building, within what your plan allows:

For Trading Apps:

• 1m, 5m - Real-time trading (Dev or Pro)
• 1h, 6h - Swing trading
• 24h - Position trading

For Analytics Dashboards:

• 24h - Daily summaries
• Use daily data and aggregate for weekly/monthly views

For Research:

• 24h over long date ranges: 30 days back on Dev, unlimited on Pro, up to 1000 candles per request

---

Production tips that’ll save you time

Cache aggressively

Historical data doesn’t change - cache it locally:

# Check when pool was created to avoid requesting non-existent data
curl "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640" | jq '.created_at'

Handle data gaps

Some pools have quiet periods. Here’s how to deal with gaps:

# Filter out low-volume periods that might have unreliable prices
curl "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/ohlcv?start=-24h&limit=24&interval=1h&inversed=true" | jq '.[] | select(.volume > 1000)'

Multi-pool strategy

For major tokens, cross-reference data from multiple pools:

# Get the top USDC pools to compare price consistency
curl "https://api.dexpaprika.com/networks/ethereum/pools/search?token_address=0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48&limit=5" | jq '.results[] | .id'

Rate limiting

Don’t hammer the API. Keyless requests are capped at 15 a minute and free-key requests at 30, and Pro lifts that to 500 a minute. Batch your requests and cache results:

// Example: Batch multiple token histories
const tokens = ['USDC', 'WETH', 'USDT'];
const historyPromises = tokens.map(token => 
  fetch(`/api/history/${token}`).then(r => r.json())
);
const allHistories = await Promise.all(historyPromises);

---

Troubleshooting common issues

”Empty response”

Pool might not have data for your date range:

# Check pool age first
curl "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640" | jq '.created_at'

“Weird price spikes”

You hit a low-liquidity period. Switch to longer intervals or higher-volume pools:

# Use 6h intervals to smooth out anomalies
curl "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/ohlcv?start=-24h&interval=6h&limit=4&inversed=true"

“Upside-down prices”

You need the inverted ratio:

# Flip from TOKEN/ETH to ETH/TOKEN
curl "https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/ohlcv?start=-24h&interval=1h&inversed=true&limit=10"

“403 Forbidden”

The request asked for more history or finer candles than your plan allows. The message says which plan lifts the limit:

{"message":"OHLCV history beyond the last 24 hours requires an API key (free key: 7 days, Dev plan: 30 days, Pro plan: unlimited)"}

Move start inside the window, pick a coarser interval, or send a key. A 403 is not worth retrying unchanged.

---

What’s next?

Pool details API

Get liquidity, fees, and other pool metrics.

Real-time price feeds

Combine historical data with live prices.

FAQs

What if my date range predates the pool?

First check the pool’s created_at; set start to not precede the creation time.

Which interval should I use?

For charts: 1h/24h. For anomaly smoothing: 6h/12h. For near real-time: 1m/5m, which need Dev or Pro.

Why is volume zero in some windows?

No trades occurred in that interval; aggregate longer or switch pools with higher activity.

How do I invert the pair?

Pass inversed=true to flip from token0/token1 to token1/token0.

Need help?

Discord community

Ask questions and see what others are building.

Direct support

Hit a wall? We’ll help you debug it.