Understand Tuteliq's rate limiting: per-plan quotas, burst limits, retry strategies, and how to handle 429 responses.

Tuteliq uses rate limiting to ensure fair usage and platform stability. Limits are based on your subscription tier.

Limits by Plan

Plan

API Calls/Month

Requests/Minute

Latency

Free (development)

1,000

60

~1.2s

Build

25,000

600

Assure

150,000

3,000

Enterprise

Unlimited

Custom

Dedicated (sub-400ms on dedicated hardware)

Rate Limit Headers

Every API response includes headers to help you track your usage:

Header

Description

X-RateLimit-Limit

Maximum requests allowed per minute

X-RateLimit-Remaining

Requests remaining in current window

X-RateLimit-Reset

Unix timestamp when the window resets

X-Monthly-Remaining

API calls remaining for the billing period

Handling Rate Limit Errors

When you exceed rate limits, the API returns a 429 Too Many Requests response:

Rate Limit Exceeded

Implement exponential backoff and retry logic. Check the Retry-After header for wait time.

Best Practices

Need Higher Limits?

Upgrade your plan or purchase additional credits to increase your monthly quota.

Get Started Free · Read Documentation · View Pricing