The number of requests an API client can perform is subject to limitation depending on how the API Key is configured.
Moreover, there is a limit that is globally applied to the environment, and by default is 2000 requests/minute, if you need more, you must contact Servitly support.
When an API request is received, the backend verifies the rate limit according to the API Key used by the client, after that verifies also the overall environment limit.
If one of the rate limits is exceeded, the HTTP error code 429 is returned.
The rate limit configured on the API Key depends also on its restrictions, in the case of None or Website the rate limit is computed as total among all clients using such key, instead in the case of Mobile App the rate limit is computed per device.
Rate limits are verified through a bucket based on a one-minute sliding window. A token is consumed for each request, and the bucket ensures a certain amount of tokens per period of time.
In case of Hours or Days as for Max request time unit, the period is subdivided into slots of one minute length, each of which has a certain number of tokens depending on the rate limit.
When the client runs out of tokens, the excess requests are refused, and to perform new requests the client has to wait one minute to get more tokens.
Example 1
Suppose a rate limit of 600 data requests/hour, this means you can perform 10 requests per minute.
When exceeded, you have to wait 1 minute to make other 10 requests.
Example 2
Suppose a rate limit of 24 * 60 data requests/day, this means you can perform 1 requests per minute.
When exceeded, you have to wait 1 minute to make another request.
Example 3
Suppose a rate limit of 100 data requests/minute, this means you can perform 100 requests per minute.
When exceeded, you have to wait 1 minute to make other 100 requests.