Pro API: authenticated access on api-pro.dexpaprika.com

api-pro.dexpaprika.com serves paid plans only and needs your API key in the Authorization header. What to send, what each error means, and how to move an existing integration across.

api-pro.dexpaprika.com serves paid plans only. Every request to it needs your API key in the Authorization header, sent as the entire header value with no scheme word in front of it.

If you are keyless or on a free key, this is not your host. Build against api.dexpaprika.com, where the same endpoints, paths and parameters answer with the same data. Get or copy your key in console.dexpaprika.com, compare plans on pricing, and if you already have a working free-tier integration, upgrading to Pro is the whole list of changes it needs.

A request that works

curl "https://api-pro.dexpaprika.com/networks" \
  -H "Authorization: api_YOUR_KEY"

If your request just failed

What you sent	What comes back
No Authorization header, on /	401 and JSON: {"message": "missing or invalid api key"}
No Authorization header, on a data path	403 and an HTML block page from the edge, with no JSON body
A key we do not recognise	401 and JSON: {"message": "api key verification has failed"}
A free key	403 and JSON carrying "error": "wrong_host", naming api.dexpaprika.com as your host
A paid key, but to api.dexpaprika.com	the same wrong_host 403 pointing back here, except on paths the free host already has cached, which answer 200 with free-tier data marked x-api-plan: keyless

The HTML body is the one that surprises people. This host sits behind an edge rule that can reject a request before it reaches the API, and that rule answers with an HTML page rather than the JSON everything else here returns. Treat an HTML body as a prompt to check the header and the base URL first, before you regenerate anything. Every status code and body is listed on error handling.

What Pro changes

Both hosts serve the same data: the same endpoints, the same 36 chains, the same history. What changes is freshness, headroom and support. Free-tier responses can be up to 15 seconds behind; Pro is real time. Pro also raises the monthly credit allowance and the per-minute rate, carries a 99.5% SLA, and includes priority support. Current numbers for every tier are on rate limits and pricing.

Enterprise is this same host and this same API, with the limits set per contract.

---

Getting started

1. Get your API key

Pro is self-serve. You do not need to talk to anyone to start.

1. Create your account

   Sign up at console.dexpaprika.com. No card is required to create the account.

2. Subscribe to Pro

   Pick Pro on the pricing page at $99/month, or$1,032 billed annually. Enterprise is the same API with limits agreed per contract; that one does start with a conversation.

3. Copy your key

   Your key is under Keys in the console. Each account has a single API key, so this is the one you use everywhere.

Open the console

Create an account, manage your subscription, and read your usage

Customer portal

Create your API key and track credit usage

Enterprise is the one that goes through us. Email the team for custom limits, unmetered streaming and a 99.95% SLA.

Building on the free tier first is the right move: api.dexpaprika.com needs no key at all and serves the same data. Come here when you hit the ceiling.

2. Authentication

All Pro API requests require authentication via the Authorization header:

cURL

curl "https://api-pro.dexpaprika.com/networks/ethereum/pools/search" \
    -H "Authorization: api_YOUR_API_KEY_HERE"

3. API key format

Your API key will follow this format:

api_your_personal_api_key

Your key already starts with api_. Send it exactly as the console shows it, as the entire value of the Authorization header, with nothing added in front.

Send the key as the entire Authorization header value, nothing before it and nothing after it. If your HTTP client only offers a token field that prepends a scheme word, do not use it; set a raw header instead. On api-pro.dexpaprika.com a request the edge does not recognise is answered with a 403 HTML page rather than a JSON error body, so do not assume every failure parses as JSON.

---

Differences from the free API

Feature	Free API	Pro API
Base URL	https://api.dexpaprika.com	https://api-pro.dexpaprika.com
Authentication	None required	API key required
Monthly credits	50,000 keyless, 300,000 with a free key	5,000,000 included, then $20 per additional 1M
Requests per minute	15 keyless, 30 with a free key	300
Max data delay	15 seconds	real time
SLA	best effort	99.5%
Infrastructure	Shared	Dedicated
Support	Community	Priority support
REST endpoints	All endpoints	All endpoints
SSE streaming	36 public token streams keyless; any token, up to 10 concurrent, with a free key	metered

Credit detail lives on the rate limits page, and plans on pricing. Every REST endpoint, all history and all 36 chains are available on the free tier as well; what the paid plans change is freshness, allowance, streaming scope and support. Enterprise is this same API with the limits raised for your workload, so everything below applies unchanged.

All REST endpoints available in the free API are also available in the Pro API. Simply replace the base URL and add authentication.

---

Quick start example

Let’s fetch Solana SOL token data using the Pro API:

1. Prepare your request

   Replace YOUR_API_KEY_HERE with your actual API key:

   curl "https://api-pro.dexpaprika.com/networks/solana/tokens/So11111111111111111111111111111111111111112" \
       -H "Authorization: api_YOUR_API_KEY_HERE"
   
2. Receive the response

   The same data the free API returns, captured live. The 30m, 15m, 5m and 1m interval objects and the social links are trimmed here for length; the real response carries them:

   Response

   {
     "id": "So11111111111111111111111111111111111111112",
     "name": "Wrapped SOL",
     "symbol": "SOL",
     "chain": "solana",
     "decimals": 9,
     "total_supply": 9729104.429281628,
     "has_image": true,
     "added_at": "2026-08-10T14:20:16Z",
     "price_stats": {
       "high_24h": 97.72851812469702,
       "low_24h": 92.53839547091638,
       "ath": 2094.381880389729,
       "ath_date": "2025-02-18T22:43:00Z"
     },
     "summary": {
       "chain": "solana",
       "id": "So11111111111111111111111111111111111111112",
       "price_usd": 95.00021242163845,
       "fdv": 924266987.4540582,
       "liquidity_usd": 553757948.2095541,
       "pools": 79958,
       "24h": {
         "volume": 55022471.30115615,
         "volume_usd": 5215005748.220995,
         "sells": 15117657,
         "buys": 8886063,
         "txns": 24126210,
         "buy_usd": 2528611480.8570423,
         "sell_usd": 2686394267.3639526,
         "last_price_usd_change": 1.36503236687871
       },
       "6h": {
         "volume": 15008105.889129847,
         "volume_usd": 1415167906.7786279,
         "sells": 3848462,
         "buys": 2257851,
         "txns": 6135660,
         "buy_usd": 686184008.4416271,
         "sell_usd": 728983898.3370007,
         "last_price_usd_change": 0.8177448219626
       },
       "1h": {
         "volume": 2522513.1508265836,
         "volume_usd": 239070465.79418552,
         "sells": 694311,
         "buys": 363197,
         "txns": 1063751,
         "buy_usd": 115287924.18944858,
         "sell_usd": 123782541.60473694,
         "last_price_usd_change": 0.20697823770267
       }
     },
     "last_updated": "2026-08-24T10:33:47.365548003Z"
   }
   

---

Error handling

Authentication errors

403 and an HTML page saying you have been blocked

The response is not JSON. The body is an HTML page headed “Sorry, you have been blocked” with a Cloudflare ray ID.

What it means: the request reached this host carrying no Authorization header at all, so it was stopped at the edge before the API saw it. It is not an IP ban and there is no cooldown: the next request with a header is served normally.

Solution: send your key in the Authorization header. If you are parsing responses as JSON, check the content type first, because this one will not parse.

401 Unauthorized - no key, or a key we do not recognise

Error response:

{
  "message": "api key verification has failed"
}

The host root answers {"message": "missing or invalid api key"} for the same reason.

Solution: the header arrived but its value is not a key we know. Copy the key again from console.dexpaprika.com. Each account has exactly one key and regenerating has no overlap window, so if you regenerated it, every integration needs the new value.

403 Forbidden - the key and the host disagree

A key that is valid for one plan sent to the other plan’s host returns a structured wrong_host body naming the host to use.

Solution: match the host to your plan. Keyless traffic and free keys go to api.dexpaprika.com and streaming.dexpaprika.com; paid keys go to api-pro.dexpaprika.com and streaming-pro.dexpaprika.com. Paths, query parameters and response shapes are identical, so only the base URL changes. Full detail on 403 Forbidden (wrong host), and the whole switch is in upgrading to Pro.

Other errors

All other error codes match the standard DexPaprika API:

• 400 Bad Request - Invalid parameters
• 402 Payment Required - monthly credit allowance exhausted. Retrying does not help. Add credits from pricing, or turn on autoscaling in console.dexpaprika.com to let usage run past the cap up to your spend limit. See error handling
• 404 Not Found - Resource not found
• 429 Too Many Requests - per-minute rate exceeded. Retry after the Retry-After header
• 500 Internal Server Error - Server error

---

Available endpoints

The Pro API provides access to all DexPaprika endpoints:

Tokens

Get detailed token information including price, liquidity, and trading volume

Pools

Access liquidity pool data and trading statistics

Networks

List all supported blockchain networks

Pool transactions

Query swap transactions, adds, and removes

Search

Search across tokens, pools, and DEXes

Batched prices

Retrieve multiple token prices in a single request

View complete API documentation in the REST API Reference section. All examples use the free API URL - simply replace with api-pro.dexpaprika.com and add authentication.

---

Migration guide

Moving an existing free-tier integration across takes two changes: the base URL, and your key in the Authorization header on every request. The full walkthrough, with before and after code in four languages, what each failure looks like on the wire, and a checklist to run before you deploy, is on upgrading to Pro.

---

Best practices

Secure your API key

Never expose your API key in client-side code or public repositories.

• Store API keys in environment variables or secure vaults (e.g., AWS Secrets Manager, HashiCorp Vault)
• Use .env files locally and add them to .gitignore
• Rotate keys periodically as part of security best practices
• Never hardcode keys in your application source code

Example .env file

DEXPAPRIKA_PRO_API_KEY=api_your_personal_api_key

Monitor your API usage

Track your API usage to optimize performance and identify issues early.

• Watch credit spend against your allowance in console.dexpaprika.com, or call GET https://api-pro.dexpaprika.com/usage with your key in the Authorization header; requests_used, requests_left and the period dates come back only for an authenticated call on that host
• Log all API requests and responses for debugging
• Set up monitoring dashboards to track request volumes
• Monitor response times and error rates
• Alert on unusual patterns or spikes in traffic
• Review usage patterns to optimize your integration

Implement robust error handling

Always handle authentication errors gracefully and implement retry logic.

• Treat 401 and 403 as configuration faults, not key faults: check the header and the base URL before touching the key
• Implement exponential backoff for transient failures
• Don’t retry on authentication errors; fix the header or the base URL first
• Log errors with context for easier troubleshooting
• Provide meaningful error messages to end users

Example error handling

try {
  const response = await fetch(url, { headers });
  if (response.status === 403) {
    // On api-pro a 403 means the request was rejected before the API saw it, or the
    // key belongs to the other host. Check that the Authorization header is present
    // and holds the key alone, and that the base URL is api-pro.dexpaprika.com.
    // Do not regenerate the key: there is one key per account, and regenerating it
    // breaks every other integration at once.
    return;
  }
  if (response.status === 401) {
    // The header is missing, or the key was not recognised. Fix the header, do not retry.
    return;
  }
  // Handle other errors with retry logic
} catch (error) {
  console.error('Request failed:', error);
}

Use connection pooling

Reuse HTTP connections to reduce latency and improve throughput.

• Configure HTTP clients to reuse connections
• Set appropriate connection pool sizes (e.g., 10-50 connections)
• Enable keep-alive headers
• Use persistent connections for high-volume applications
• Monitor connection pool metrics

Example with Python requests

import requests
from requests.adapters import HTTPAdapter

session = requests.Session()
adapter = HTTPAdapter(pool_connections=20, pool_maxsize=20)
session.mount('https://', adapter)

# Reuse session for all requests
response = session.get(url, headers=headers)

---

Next steps

REST API reference

Explore all available endpoints and their parameters

Streaming API

Real-time token price updates over Server-Sent Events. On Pro, connect to streaming-pro.dexpaprika.com.

Tutorials

Learn how to build applications with DexPaprika

Coverage checker

Check which tokens and pools are available in our database

---

Get support

Enterprise support

Get priority technical support from our engineering team

Join Discord

Connect with our community for general questions

---

FAQs

How do I get a Pro API key?

Sign up at console.dexpaprika.com, subscribe to Pro, and copy the key from the Keys page. No sales call and no waiting. Enterprise is the exception: those limits are agreed per contract, so email [e-mail].

Can I use both the free and the Pro API at once?

You can call api.dexpaprika.com without a key from the same application, and that keyless traffic is metered on free-tier terms. What you cannot do is use your paid key on both hosts: a key is bound to the plan’s host, and sending a paid key to the free host answers 403 wrong_host. Pick the host that matches the key you are sending.

What are the Pro limits?

5,000,000 credits a month included, at up to 300 requests a minute, with $20 per additional 1M beyond that. One request costs one credit, batch endpoints cost one credit per item, and each streaming update delivered costs one credit. Enterprise raises both numbers to fit your workload. See rate limits and pricing; these numbers move.

What happens if my API key is compromised?

Regenerate it yourself from the Keys page in the console. Because each account has exactly one key, regenerating replaces the old one immediately, so plan a moment when you can redeploy: every integration using the old key stops working at once. If you cannot get into the account, email [e-mail].

Do you offer dedicated infrastructure or on-premise deployment?

Yes, we can provide custom infrastructure solutions for enterprise customers. Contact our sales team to discuss your specific requirements.

How do I tell whether the problem is me or you?

Two different questions, two different calls. GET /usage tells you which plan and which host you are really talking to, and it is never served from cache, so it is the one to reach for when a key or a base URL is in doubt. Separately, every host answers GET /health with a plain up or down for the service itself. It takes no key and says nothing about your key, your plan or your host, so it only answers “is the service running”, never “is my request right”.

Is the data the same as the free API?

The coverage is identical: same endpoints, same chains, same history. The difference is freshness. The free tier is served with a delay of up to 15 seconds; Pro is real time. Pro also adds dedicated infrastructure, a much higher credit allowance, a 99.5% SLA and priority support.