With the upcoming API limits being enforced, I wanted to confirm whether Toggl will continue using a leaky bucket rate-limiting system. Specifically, is it still acceptable to handle 429 Too Many Requests responses by backing off and retrying later?
We’ve built a system that syncs project data and time entries between our ticketing system and Toggl. With the new limits, it may become more challenging to keep this integration fully compliant.
Any clarification on how the new rate limits work—or recommended best practices for staying within them—would be greatly appreciated. Thanks!
Hi @hejdamax, there should be no change made to the leaky bucket rate-limiting approach. Also, I can now share that the limits originally communicated with our users via email will likely change, as well as the date when they will be implemented, due to user feedback. More info to come soon.
Thank you very much. I will await any news that will come. It would be a shame if Toggl became unusable for many people due to overly restrictive API limits.