Business analysis glossary
Rate Limiting
What it is
Rate limiting caps how many requests a client can send to an API in a period, such as one hundred requests per minute. Requests over the limit are refused, usually with status 429 Too Many Requests and a header saying when to retry.
Why it matters
Rate limits protect systems from overload, abuse and runaway scripts, and they shape how partners integrate. Analysts should capture limits as non functional requirements, check that partner volumes fit within them and define what users see when a limit is reached.
Example
A partner wants to check the status of ten thousand shipments every five minutes, but the tracking API allows two hundred requests per minute. The analyst proposes a webhook for status changes instead, which cuts the partner's calls by more than ninety percent and stays within the limit.