Rate Limits

⚡ Overview

To ensure fair usage and platform stability, all API requests are subject to rate limits. Limits are applied per workspace and tracked across three rolling time windows: per minute, per hour, and per day.

📊 Default Limits

The following default limits apply to all workspaces. Custom limits may be configured for your workspace based on your plan.

🔍 Check Your Limits

Use this endpoint to retrieve your current rate limit usage for the current minute, hour, and day.

{
  "status": "success",
  "success": true,
  "message": "You are within the rate limit",
  "data": {
    "limits": {
      "perMin": 20,
      "perHour": 50,
      "perDay": 100
    }
  }
}

🚫 Error Responses

When you exceed a rate limit, the API responds with HTTP 429 and a descriptive error message indicating which window was exceeded.

{
  "error": "Minute rate limit exceeded. Please try again in a minute."
}

💡 Best Practices

Follow these guidelines to make the most of your API quota and avoid hitting rate limits.

• Implement exponential backoff — When you receive a 429 response, wait for increasing intervals before retrying (e.g., 1s → 2s → 4s → 8s).
• Check limits proactively — Call GET /v1/ratelimit/limits to monitor your remaining quota before sending bulk requests.
• Batch where possible — Combine multiple operations into fewer requests to reduce your call count.
• Cache responses — Store read-only data locally and refresh only when necessary to avoid redundant API calls.
• Spread requests evenly — Distribute API calls across the full time window instead of bursting them at the start.
• Handle errors gracefully — Your integration should degrade gracefully when rate-limited, queuing work for retry rather than dropping it.

Need Higher Limits?

If your use case requires higher throughput, contact our team to discuss plan upgrades and custom rate limit configurations.