Overview
The Jmpy.me API implements rate limiting to ensure fair usage and maintain service stability. Rate limits vary based on your subscription plan and the type of endpoint.Rate Limit Headers
Every API response includes rate limit information in the headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the current window |
X-RateLimit-Remaining | Remaining requests in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit resets |
Example Response Headers
Rate Limits by Plan
- Free
- Pro
- Enterprise
| Endpoint Type | Limit |
|---|---|
| URL Creation | 50/day |
| URL Reads | 500/day |
| QR Generation | 25/day |
| QR Reads | 250/day |
| Analytics | 100/day |
Handling Rate Limit Errors
When you exceed rate limits, the API returns a429 Too Many Requests response:
Best Practices
Implement Exponential Backoff
Implement Exponential Backoff
When you receive a 429 error, wait before retrying:
Cache Responses
Cache Responses
Cache read responses to reduce API calls:
Batch Operations
Batch Operations
Use batch endpoints when available to reduce the number of API calls.Instead of creating URLs one by one:Use bulk import:
Monitor Usage
Monitor Usage
Track your API usage in the dashboard and set up alerts before hitting limits.
Need Higher Limits?
Upgrade Plan
View our pricing plans for higher rate limits
Enterprise
Contact us for custom enterprise solutions