Rate Limits

Rate Limit Overview

To ensure fair usage and maintain service quality, the Ábyrg verslun API implements rate limiting on all endpoints. Rate limits are applied per API key.

Current Limits

Rate Limit Headers

Every API response includes headers with rate limit information:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1709827200

• X-RateLimit-Limit: Maximum requests allowed in the current window
• X-RateLimit-Remaining: Number of requests remaining in the current window
• X-RateLimit-Reset: Unix timestamp when the rate limit resets

Handling Rate Limits

When you exceed the rate limit, the API returns a 429 status code:

{
  "error": "Rate limit exceeded",
  "retryAfter": 45
}

Best Practices

• Monitor rate limit headers in API responses
• Implement exponential backoff for retries
• Cache responses when possible to reduce API calls
• Use webhooks for real-time updates instead of polling
• Contact support if you need higher limits for your use case