Rate Limiting

To keep the reev API fast and reliable for everyone, we apply rate limits to all incoming requests. These limits prevent abuse, reduce server load, and ensure that each developer gets a fair share of system resources.

If your application makes too many requests in a short time, you may need to wait before continuing.

Current Limits

Type	Limit	Time Window
Authenticated requests	1000 requests per API key	per hour
Unauthenticated requests	60 requests per IP address	per minute

Note: Authenticated and unauthenticated traffic is tracked separately.

What Happens If You Go Over

If you exceed your rate limit:

The API responds with HTTP 429 Too Many Requests

Example Response

{
  "code":429,
  "message":"Too Many Requests"
}

Best Practices

To stay within the limits:

Use pagination for large result sets
Cache repeatable data when possible
Avoid sending request bursts—spread them out
Handle 429 errors with retry logic and backoff

Need Higher Limits?

If your app needs more capacity, contact our support team to request a higher rate limit.