Timery 1.7.2 is now available with more changes & optimizations to address the new Toggl API limits and reduce Timery’s API usage as well as with some general improvements & fixes.

https://apps.apple.com/app/id1425368544

Next up will be working on AppleOS 26 updates.

Thank you for using Timery and being part of the Timery Club. Your support means so much!

‎Timery for Toggl

‎Enhance your Toggl time-tracking experience with Timery! Start your most-used timers with one click. Edit your time entries easily. See reports of your time tracked. With its apps, widgets, and Shortcuts actions, Timery brings you easy time tracking with Toggl. Timery works on Mac, iPhone, iPad, an…

App Store

How have you been doing with the API limits? Have you been staying under them? Are you hitting either or consistently getting close?

Dealing with the Toggl changes will continue to be a work in progress. I’ll still be trying to find what more I can do and if I’m missing or overlooking something that can be improved.

Thank you again for all your support. And happy time tracking!

https://apps.apple.com/app/id1425368544

‎Timery for Toggl

‎Enhance your Toggl time-tracking experience with Timery! Start your most-used timers with one click. Edit your time entries easily. See reports of your time tracked. With its apps, widgets, and Shortcuts actions, Timery brings you easy time tracking with Toggl. Timery works on Mac, iPhone, iPad, an…

App Store
@timery I've been doing totally fine with the API limits until today. I think something might be going wrong because I hit the limits two times today, and during one of those times I was on a walk so as far as I was aware I wasn't making any API calls at all. Do you know if there's a way to audit the API calls, either from Toggl or from Timery? I'm curious if I instigated the behaviour somehow.