You are being rate limited. The response should carry Retry-After, and usually X-RateLimit-Limit, -Remaining and -Reset.
Test that your client backs off on Retry-After rather than retrying immediately — an aggressive retry on a 429 is how a slowdown becomes an outage.
1 endpoint in this playground answers with 429. Every one is free, needs no signup, and can be called from the browser or with curl.
GET https://funapi.dev/api/coffee/v1/rush-hour — Too many requests — wait for Retry-After seconds (Coffee Shop API)All HTTP status codes · All 37 mock REST APIs · Getting started guide