429 Too Many RequestsWhat 429 Too Many Requests means
HTTP 429 is the standard rate-limiting response. Servers track request volume against a quota — commonly requests per minute per IP address, but also per API key, per account, per session cookie, or per endpoint — and answer 429 once you cross it. Many include a Retry-After header stating how many seconds to wait, or X-RateLimit-* headers showing your quota and reset time.
The most important diagnostic question is what the limit is keyed on. If it is keyed on your IP, spreading requests across more IPs solves it directly. If it is keyed on an API key, account, or session, no amount of IP rotation helps — ten IPs sharing one token still count as one client. Read the response body and headers; APIs usually say which.
Also distinguish 429 from soft blocking. A real 429 is a well-behaved throttle that resets on schedule. If you see CAPTCHAs, 403s, or empty 200s alongside it, the site has escalated past rate limiting into bot detection, which needs a different response — better request hygiene, not just slower requests.