Kraken Exchange Error Code EAPI: How to Fix Rate Limit Exceeded
Medium 30-60 minutes High Severity
Verified June 2026
- Error Code
- EAPI:Rate limit exceeded
- Brand
- Kraken
- Product Type
- crypto_exchange
- Severity
- High
- DIY Difficulty
- Medium
- Estimated Fix Time
- 30-60 minutes
Ad
Tools You'll Need
- Text editor or IDE
- API testing tool (Postman/curl)
- Trading application or bot
How to Fix Error Code EAPI:Rate limit exceeded
-
Check Current API Usage
-
Implement Rate Limiting in Your Code
Never remove rate limiting entirely as this can result in permanent API access suspension -
Use Batch Operations When Possible
-
Optimize API Call Frequency
-
Create Separate API Keys
Store API keys securely and never share them publicly or in code repositories -
Monitor and Log API Usage
Ad
When to Call a Professional
Contact a developer if you're unable to modify your trading bot code, or reach out to Kraken support if rate limits seem unusually restrictive for your trading volume and account tier.Frequently Asked Questions
How long does the Kraken rate limit last?
Kraken rate limits typically reset within 1-10 minutes depending on the severity. The standard rate limit allows 1 call per second, and the counter resets on a rolling window basis.
Can I increase my Kraken API rate limit?
Higher-tier Kraken accounts (Intermediate and Pro) may have increased rate limits. Contact Kraken support to discuss rate limit increases for legitimate high-frequency trading needs.
What's the maximum number of API calls per minute on Kraken?
Kraken typically allows up to 60 calls per minute (1 per second) for standard accounts. Some endpoints have lower limits, and batch operations may have different restrictions.
Why does my trading bot keep hitting rate limits?
Common causes include polling too frequently, making redundant API calls, running multiple bots with the same API key, or not implementing proper rate limiting in your code.
Does Kraken rate limiting affect websocket connections?
No, websocket connections have separate limits and are generally more efficient for real-time data. Consider using websockets for live price feeds instead of repeated REST API calls.