Technical / API
Rate Limiting
A control that caps how many API requests a client can make within a given time window.
In simple terms
Rate limiting is the bouncer saying 'you can only make 100 requests per minute' to protect the system from overload.
Real-world example
A bedbank API allows 500 requests per second and returns a 429 error if a client exceeds that.
Why it matters
Rate limiting protects shared infrastructure — understanding it is essential to designing efficient, non-abusive integrations.
Common mistake
Not implementing exponential backoff on 429 errors, causing a retry storm that gets a partner's API key suspended.
Interview question
How should an integration handle repeated 429 (rate limit) errors from a partner API?
Related terms
API GatewayRetry LogicHTTP 429
