Rate limits

Each API key has its own rate-limit budget. By default:

• 60 requests per minute
• 1,000 requests per hour

These are per-key, sliding-window limits. If you hit the limit you’ll get a 429 Too Many Requests response with a Retry-After header telling you how many seconds to wait.

Response headers

Every successful request (and most error responses) includes:

When you exceed a limit

1
HTTP/1.1 429 Too Many Requests
2
Retry-After: 12
3
Content-Type: application/json
4
5
{
6
  "error": {
7
    "type": "rate_limit_error",
8
    "code": "rate_limit_per_minute",
9
    "message": "Rate limit exceeded: 60 requests per minute. Retry in 12s."
10
  }
11
}

Handling

• Honor the Retry-After header — it’s the simplest correct strategy.
• For batch workloads, use the X-RateLimit-Remaining-* headers to pace yourself proactively instead of waiting for a 429.
• Use exponential backoff if you see repeated 429s — they suggest you’re hammering the limit faster than the window resets.

Need higher limits?

If your use case requires more, contact us — we can set per-key overrides via rate_limit_per_minute and rate_limit_per_hour columns. Reach out at support@telecho.io with your expected request profile.