Skip to content
GlossaryConceptUpdated May 2026

Rate Limiting

noun · also: rate-limit, exponential-backoff, retry

What is rate limiting?

Rate limiting is when an API restricts how many requests you can make in a given time window — common to all production APIs.

Definition

Full definition of rate limiting

Most APIs limit per second (100 req/s), per minute (1000 req/min), or per day (10K req/day). When you exceed the limit, you get HTTP 429 with a Retry-After header. Tiny Command auto-handles rate limits by queuing and backing off. Critical to design for: bulk operations need throttling, not parallelism.

In practice

Rate Limiting examples

Stripe rate limit
100 req/sec for live mode, 25 req/sec for test mode, per account.
Used by

Apps that exemplify rate limiting

See rate limiting in action across real integrations.

FAQ

Common questions about rate limiting

What's the difference between rate-limit and quota?
Rate-limit = per second/minute (throughput). Quota = per day/month (volume). You can hit either.
Can I request a higher rate limit?
Usually yes, contact the API provider with use-case justification. Often free for legitimate volume.