Rate Limits

Overview

All LucidSource Public API requests are subject to rate limiting. This ensures fair usage and platform stability for all clients.

Rate Limit

Limit

Window

60 requests

Per minute, per API user

The rate limit applies uniformly across all API endpoints. All endpoints share the same 60 requests/minute budget, so calls to different endpoints count toward the same limit.

What Happens When You Exceed the Limit

When you exceed 60 requests within a one-minute window, the API responds with:

  • HTTP Status: 429 Too Many Requests

  • Retry-After header: The number of seconds to wait before making another request.

  • Response body:

    {
  "detail": "Request was throttled. Expected available in X seconds."
}

Best Practices

  • Respect the Retry-After header - When you receive a 429 response, wait for the number of seconds indicated before retrying.

  • Use exponential backoff - If you receive repeated 429 responses, increase the wait time between retries exponentially rather than retrying at a fixed interval.

  • Spread requests evenly - Distribute requests across the minute (~1 request per second) instead of sending them in bursts.

  • Cache responses when possible - Avoid redundant API calls by caching data that does not change frequently.

Need a Higher Limit?

If the default rate limit does not meet your integration needs, contact our support team to discuss options.