Documentation Index
Fetch the complete documentation index at: https://docs.dexpaprika.com/llms.txt
Use this file to discover all available pages before exploring further.
api.dexpaprika.com is available for everyone. This Pro API is for enterprise customers who need higher performance, no rate limits, and dedicated support.What is the Pro API?
The DexPaprika Pro API provides the same comprehensive DEX and on-chain data as our free API, but with enterprise-grade infrastructure and benefits:No Rate Limits
Dedicated Infrastructure
Priority Support
API Key Authentication
Getting started
1. Get your API key
To obtain a Pro API key:Contact Enterprise Sales
2. Authentication
All Pro API requests require authentication via theAuthorization header:
3. API key format
Your API key will follow this format:api_ when using it in the Authorization header.
Differences from Free API
| Feature | Free API | Pro API |
|---|---|---|
| Base URL | https://api.dexpaprika.com | https://api-pro.dexpaprika.com |
| Authentication | None required | API key required |
| Rate Limits | 10,000 requests/day | No limits |
| Infrastructure | Shared | Dedicated |
| Support | Community | Priority enterprise support |
| Endpoints | All endpoints | All endpoints |
Quick start example
Let’s fetch Solana SOL token data using the Pro API:Error handling
Authentication errors
403 Forbidden - Missing or invalid API key
403 Forbidden - Missing or invalid API key
Authorization header with a valid API key in the format api_YOUR_KEY.401 Unauthorized - Malformed API key
401 Unauthorized - Malformed API key
Other errors
All other error codes match the standard DexPaprika API:400 Bad Request- Invalid parameters404 Not Found- Resource not found500 Internal Server Error- Server error
Available endpoints
The Pro API provides access to all DexPaprika endpoints:Tokens
Pools
Networks
Pool Transactions
Search
Batched Prices
api-pro.dexpaprika.com and add authentication.Migration guide
Migrating from the free API to Pro API is straightforward:Remove rate limiting logic (optional)
Best practices
Secure your API key
Secure your API key
- Store API keys in environment variables or secure vaults (e.g., AWS Secrets Manager, HashiCorp Vault)
- Use
.envfiles locally and add them to.gitignore - Rotate keys periodically as part of security best practices
- Never hardcode keys in your application source code
Monitor your API usage
Monitor your API usage
- 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
Implement robust error handling
- Catch and handle 403/401 errors separately from other errors
- Implement exponential backoff for transient failures
- Don’t retry on authentication errors - fix the key instead
- Log errors with context for easier troubleshooting
- Provide meaningful error messages to end users
Use connection pooling
Use connection pooling
- 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
Next steps
REST API Reference
Streaming API
Tutorials
Coverage Checker
Get support
Enterprise Support
Join Discord
FAQs
How do I get a Pro API key?
How do I get a Pro API key?
Can I use both free and Pro API simultaneously?
Can I use both free and Pro API simultaneously?
Are there really no rate limits?
Are there really no rate limits?
What happens if my API key is compromised?
What happens if my API key is compromised?
Do you offer dedicated infrastructure or on-premise deployment?
Do you offer dedicated infrastructure or on-premise deployment?
Is the data the same as the free API?
Is the data the same as the free API?