You can't somehow stop your program from spamming GGG with requests? I'm sure some sort of small delay would prevent it.

That's exactly what "throttling activated" means. GGG will only allow a certain number of requests per minute, if Procurement has got close to the limit allowed per minute, the throttling kicks in and it has to wait out the rest of the time until it can continue sending requests. If it just wants a few seconds and starts firing off requests too quickly it will still be within the same time frame, and GGG will send back an error for too many requests.

I tried it and it's a really cool software. I just learned I can get chaos & gcp with some garbage item in my stash, woot!

I don't know if you are aware of it but there is a bug with the interface under Windows 7 because of the automatic window repositioning option. When the window is moved to the edge of the screen, the interface get smaller and smaller and smaller and there is no way to resize it.

* E-tag / last modified - It would be useful if GGG used these. we can't do anything if if they don't though
* Proxies - Run requests through multiple proxies, shouldn't be too hard. Though it is in the ethical grey area.
* Custom API - if/when GGG adds stuff to this