Bypassing 429 Too many requests?

Does anyone have insight on how catalog games such as such as

manages to handle all the http requests to the catalog api without running into the error “429 Too Many requests” issue?
my understanding is that the game makes a request to a webserver which then makes another request to the catalog api, but im imagining the thousands of servers that is connected to that one webserver, how does it still work?

ive tried doing rotating proxies paired with rotating user agents in node js on the web server, but i still get error 429 “Too many requests” after 25 requests.

var searchUrl = ''

var options = {
   proxy: randomProxy,

   headers : {
        'User-Agent': randomUserAgent,

var getRequest = https.get(searchUrl,options,(res) => {

1 Like