Please Slow Down
API rate limits, explained for junior developers and non-dev builders

Integrating a third-party API is the kind of thing that is easy to get working, but hides a lot of subtleties in the corners. Rate limiting is one of them. Almost everyone learns it the hard way, and in the same order: first you don't know rate limits exist, then you add a retry, then you discover why that retry was a bad idea, and so on, one lesson at a time, each fix revealing the next problem.
This post walks that path, step by step. It is written for junior developers, and for the tech-savvy people who sometimes end up "just connecting" an API to something. At the end of it, you will know what a 429 is, how to behave like a good citizen with someone else's API, and the one situation where paying for a higher limit is the right call.
- 0 UnawareFire everything
- 1 RetryTry again at once
- 2 Back offWait longer each time
- 3 JitterWait a random time
- 4 PaceStay under the limit
- 5 ShareOne budget for all
- 6 SaveOnly useful calls
- 7 PayBuy a higher limit
