The Toggl API docs mention.
For rate limiting we have implemented a Leaky bucket. When a limit has been hit the request will get a HTTP 429 response and it's the task of the client to sleep/wait until bucket is empty. Limits will and can change during time, but a safe window will be 1 request per second. Limiting is applied per api token per IP, meaning two users from the same IP will get their rate allocated separately.
I have not encountered this limit yet, however I wonder if it could be useful to implement an option to throttle rapid requests? Or would the view be that this be implemented in application code not the module?
Kind regards,
The Toggl API docs mention.
For rate limiting we have implemented a Leaky bucket. When a limit has been hit the request will get a HTTP 429 response and it's the task of the client to sleep/wait until bucket is empty. Limits will and can change during time, but a safe window will be 1 request per second. Limiting is applied per api token per IP, meaning two users from the same IP will get their rate allocated separately.I have not encountered this limit yet, however I wonder if it could be useful to implement an option to throttle rapid requests? Or would the view be that this be implemented in application code not the module?
Kind regards,