Skip to main content

Overview

Rate limits prevent abuse and ensure fair usage across all users.

Limits by Plan

Free Tier

  • Requests: 100/hour
  • Executions: 1,000/month
  • Concurrent: 5

Pro Plan

  • Requests: 1,000/hour
  • Executions: 100,000/month
  • Concurrent: 50

Enterprise

  • Requests: Custom
  • Executions: Custom
  • Concurrent: Custom

Rate Limit Headers

Every API response includes rate limit headers:
Headers:
  • X-RateLimit-Limit - Total requests allowed per window
  • X-RateLimit-Remaining - Requests remaining in current window
  • X-RateLimit-Reset - Unix timestamp when limit resets
  • X-RateLimit-Retry-After - Seconds until you can retry (if rate limited)

Rate Limit Exceeded

When you exceed your rate limit:

Response (429)

Handling in Code

Best Practices

1. Check Headers

2. Implement Backoff

3. Batch Requests

4. Cache Results

5. Use Webhooks

Rate Limit Tiers

Rate limits are calculated per:
  • API Token: Each token has independent limits
  • IP Address: Additional per-IP limits prevent abuse
  • Time Window: Sliding 1-hour window

Concurrent Execution Limits

Maximum concurrent executions:
  • Free: 5
  • Pro: 50
  • Enterprise: Custom

Handling Concurrency

Monitoring Usage

Check Current Usage

Response:

Usage Dashboard

Monitor your usage through Cloudflare’s dashboard or implement custom analytics in your Conductor deployment.

Configure Rate Limits

Rate limits can be configured in your conductor.config.ts:
For custom rate limiting, you can use Cloudflare’s built-in rate limiting or implement your own middleware.

Error Codes

  • RATE_LIMIT_EXCEEDED - Hourly limit exceeded
  • QUOTA_EXCEEDED - Monthly quota exceeded
  • CONCURRENT_LIMIT_EXCEEDED - Too many concurrent executions

Next Steps

Authentication

API tokens

Endpoints

API reference

Webhooks

Avoid polling

Upgrade

Increase limits