Since there’s “no longer” any desktop app for Linux, I’ve made a fairly dumb script to achieve the most important features for me: Show me if I’m tracking or not, notify me every x minutes if I’m not, and submit timeline data so I can fix tracking later if I forget or mistrack. The source is available here, but I wouldn’t recommend looking at it: GitHub - swantzter/sway-toggl: Helpful toggl stuff for sway and waybar
However, with the new API limits there’s a hard limit of 30 requests per hour for “me”-requests with no possibility to even pay myself to higher limits (the 402 response code and description rather than the old 429 is a bit misleading for these endpoints imo) making this difficult, I’d land with an, at best 2 minute delay in the data which isn’t very useful for this purpose.
Given that this is a client on a workstation, there isn’t a publicly reachable server endpoint that could be used for webhooks either, and I don’t think there’s some other efficient way I could use to monitor for changes (websockets, longpolling, SSE, etc.)
What would be the recommended new approach to get near-realtime tracking information on non-publicly-routable devices given the new limits?
Footnotes for the support team since there isn’t any good way to report it:
- The links to Toggle Track Desktop on support [dot] toggl [dot] com/en/articles/2559637-do-you-have-an-api-available links to an outdated fork of the archived old desktop client, it should maybe point to the new clients
- The swagger files on Open API | Toggl Engineering all give 404