Rate Limits
Rate limits are based on your subscription plan. Each plan defines the maximum number of API requests you can make within specific time periods.
How Rate Limits Work
Your subscription plan defines rate limits across four time periods. All limits are checked on each request - if any limit is exceeded, the request will be rejected.
| Period | Description |
|---|---|
Per Second | Maximum requests allowed per second |
Per Minute | Maximum requests allowed per minute |
Per Hour | Maximum requests allowed per hour |
Per Day | Maximum requests allowed per day |
Rate Limit Levels
Rate limits can be applied at two levels:
Plan Limits
Default limits defined by your subscription plan. Applied to all API keys under your account.
API Key Limits
Custom limits set on individual API keys. Can be more restrictive than plan limits.
Exceeding Rate Limits
When you exceed a rate limit, the API returns a429 Too Many Requestsresponse with details about which limit was exceeded.
{
"statusCode": 429,
"message": "Rate limit exceeded: 100/100 per minute"
}Note: Unlike some APIs, we do not provide a Retry-After header. You should implement your own backoff strategy based on the limit period mentioned in the error message.
Checking Your Limits
You can view your current rate limits in theMultiSave Dashboardunder your subscription details or API key settings.
Best Practices
- 1
Cache responses - Store API responses locally to reduce the number of requests.
- 2
Implement backoff - When you receive a 429 error, wait before retrying based on the limit period.
- 3
Use API key limits - Set custom limits on API keys to prevent individual integrations from exhausting your quota.
- 4
Upgrade plan - If you consistently hit limits, consider upgrading your subscription plan.