Hi @tmalust , this is something I have warned several users about when using any API: Do not abuse the api server.
This might be a result of sending too many requests within a time period. Most API will document this and will tell you what is the limit of requests per time, and if you go beyond this, you might get “banned” temporarily, and eventually permanently if you continue to abuse it.
Servers impose such limits to protect themselves from attacks.
Sending 6300 addresses in 1 shot is a lot.
So, even if you are going to use another API such as what @qqilihq suggested, if you are going to send the same way, you will be banned.
You need to send the requests in batches with some cooling time in between the batches. For example, send 100 requests every 5 seconds, meaning you send batches of 100 requests with a wait time of 5 seconds. Obviously that metric varies per api - check their documentation.
The GET/POST Request nodes already have these options embeded, so you don’t have to use Loops and the Wait node to implement the batch and delay. You can just do it in the GET/POST Request nodes. Look at the Delay and Concurrency options:
The Delay represents how many milliseconds (ms) you want to wait before sending the next batch. So 5000 ms means 5 seconds.
The Concurrency means how many rows you want to send at the same time, so that’s your number of requests per batch.
EDIT: Based on what I’m seeing online, Google has a 50 Requests per second (QPS - I think Query Per Second) rate limit. So 6300 was well over that limit.