Skip to main content

Rate Limit Overview

Card2Crypto enforces rate limits to ensure fair usage and system stability. Current Limits:
  • 100 requests per minute per API key
  • Measured using a sliding window algorithm

Rate Limit Headers

Every API response includes rate limit information in headers:

Rate Limit Response

When you exceed the rate limit, you’ll receive a 429 response:

Checking Rate Limit Status

Best Practices

1. Implement Exponential Backoff

Retry failed requests with increasing delays:

2. Use Request Queuing

Queue requests to stay within limits:

3. Monitor Rate Limit Headers

Track remaining requests and slow down proactively:

4. Cache API Responses

Reduce API calls by caching responses:

5. Batch Operations

Group multiple operations when possible:

Rate Limit Strategies

Strategy 1: Token Bucket

Strategy 2: Sliding Window

Handling 429 Responses

Automatic Retry with Backoff

Notify User

Monitoring Rate Limits

Track Usage

Rate Limit Exceptions

Some endpoints may have different limits:

Increasing Rate Limits

The default limit of 100 requests/minute is sufficient for most use cases. If you need higher limits:
  • Contact support with your use case
  • Enterprise plans may offer higher limits
  • Consider optimizing your integration first

Testing Rate Limits

Simulate Rate Limiting

Common Mistakes

1. Polling Too Frequently

2. No Retry Logic

3. Ignoring Rate Limit Headers

Next Steps

Error Reference

Handle rate limit errors properly

Webhook Overview

Use webhooks instead of polling

Node.js Guide

See rate limiting examples

Testing Guide

Test your rate limit handling