Etiquette when using web API

We don't currently limit or throttle web API access (we might in the future). What we currently do is we occasionally flag extremely high API usage and work with the developers to use the API more smartly -- which is usually as simple as caching things for a while rather than hammering the servers.

For today task I've put 2 seconds breaks between requests

Do you mean you're doing something continually (non-stop, forever) and there are 2 second breaks between this activity? If that's what you mean, then you've got a design problem. You should be caching data, and requesting data strategically.

Or do you mean you're doing "things" (short tasks that's not a continuous, never-ending process)? If so, then there's no need to do any delay between requests.

Does that make sense?

I needed to deactivate 600 activations so I called deactivate with key names 600 times.Is there a way to deactivate all at once? 🙂

For a case like that, just looping through and deactivating the keys by calling the API is the best way to do it.

But why would you want to do that? What's the problem you're trying to solve?

I am using normal license instead of TurboFloat to rent some licenses to my trusted customer so they can run it on many servers (and sometimes VM crash and the activations are lost). I know I am supposed to use TurboFloat but as it's a very rare request and the customer is a good one that was the quickest way for me to set this up.

Btw, I am sticking to 2 seconds between requests for now. I hope that way it's not a problem even if I run many requests. If there are any restrictions in the future I will comply to those of course.