Skip to content

Rate Limits

Understanding API rate limits and how to handle rate limiting responses.

In plain terms

The API limits how many requests you can make per minute (240 for most endpoints). If you exceed this, you get a 429 response with retry_after telling you how many seconds to wait. This protects the service and ensures fair usage. Contact Moveris for higher limits if needed.

Limits by Endpoint

Endpoint Rate Limit
/api/v1/fast-check 240 requests/minute
/api/v1/fast-check-stream 240 requests/minute
/api/v1/fast-check-crops 240 requests/minute

Higher Limits Available

If you need higher rate limits for your application, contact the Moveris team to discuss enterprise plans with custom limits.

Rate Limit Exceeded Response

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

{
  "data": null,
  "success": false,
  "message": "Rate limit exceeded",
  "errors": [
    { "rate_limit_exceeded": ["Rate limit exceeded"] }
  ]
}

The response may also include a Retry-After HTTP header (seconds until you can retry). Prefer that header when present.

Handling Rate Limits

  1. Read Retry-After — When the server sends this header, wait that many seconds before retrying. If the body includes errors, treat it like other API errors (see Errors).

  2. Implement exponential backoff — Start with the Retry-After value (when present) and increase wait time for subsequent failures.

  3. Queue requests — If you're making many requests, implement a queue to stay within limits.

  4. Use Fast Check for high volume — The /fast-check endpoint has the highest rate limit (240/min) for high-volume scenarios.

Best Practices

  • Monitor your request rate and stay within published limits
  • Use session IDs to batch frames rather than making separate requests
  • Cache results when appropriate to avoid duplicate requests
  • Check the Status Page if you experience unexpected rate limiting or errors