4 ms·
Yes, looking at the network requests I also get this error fairly consistently by the third or fourth batch: > {"ApiResponse":{"$":{"Status":"ERROR"},"Errors":
by grepper 11y ago
Yes, looking at the network requests I also get this error fairly consistently by the third or fourth batch:
> {"ApiResponse":{"$":{"Status":"ERROR"},"Errors":[{"Error":[{"_":"Too many requests","$":{"Number":"500000"}}]}],"Server":[""],"GMTTimeDifference":[""],"ExecutionTime":["0"]}}
Which then results in "Uncaught TypeError: Cannot read property '0' of undefined".
Cool idea, though!
- finnn 11y agoDamnit, namecheap. They must be ratelimiting me... I didn't see anything about ratelimits in the API docs, I guess I'll go re-read them
- dspillett 11y agoI would assume any API like this would have rate limits of some sort. If you are making a separate request for every TLD that is likely to be worse too.