Rate Limiting

Learn about API rate limits and how to handle them.

Rate Limits

The Slice API implements rate limiting to ensure fair usage and system stability.

Default Limits

  • Limit: 100 requests per minute per tenant
  • Window: 1 minute rolling window
  • Tracking: Per tenant (based on API key)

Rate limits are configurable via environment variables. Contact support for higher limits.

Rate Limit Headers

Every API response includes rate limit headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 2024-01-01T12:01:00Z
  • X-RateLimit-Limit - Maximum requests allowed
  • X-RateLimit-Remaining - Requests remaining in current window
  • X-RateLimit-Reset - When the rate limit window resets

Rate Limit Exceeded

When you exceed the rate limit, you'll receive a 429 Too Many Requests response:

{
  "success": false,
  "error": "Rate limit exceeded. Please try again later.",
  "retryAfter": 60
}

Best Practices

  • Implement exponential backoff when receiving 429 responses
  • Monitor rate limit headers to avoid hitting limits
  • Cache validation results to reduce API calls
  • Use batch operations when possible