Toggl Platform Update: What the Changes Mean for ToggleWear

We are sharing an important platform update that affects new users, third-party integrations, and the current landscape of ToggleWear.

If you are an existing ToggleWear user, your app continues to work normally. However, if you are a new Toggl user or setting up ToggleWear for the first time, Toggl has introduced platform changes that affect how third-party Wear OS apps connect.

What Happened?

Until recently, Toggl allowed the classic Toggl Track backend and their new platform to coexist. Users could switch back and forth freely, meaning third-party apps like ToggleWear could communicate reliably through the standard Toggl Track API.

Toggl recently eliminated that access for new accounts:

1. Forced Redirect for New Users: When a new account visits https://track.toggl.com/timer, the browser now automatically redirects to focus.toggl.com. There is no longer a setting or toggle to access the classic Toggl Track interface.
2. Grandfathered Legacy Accounts Only: Only accounts created before this cutoff retain access to the classic Toggl Track dashboard and its complete API.
3. Third-Party Integrations Suspended Platform-Wide: If you visit Toggl’s official integrations directory at toggl.com/integrations, nearly all third-party integrations now display this banner:

   "This is a legacy integration for Toggl Track which we currently don't support for Toggl"

   Toggl is currently only supporting their own in-house first-party apps for the new platform.

Why Can't ToggleWear Simply Support the New Version?

ToggleWear is a native Wear OS client that communicates directly with Toggl's backend to sync timers, projects, and complications on your smartwatch.

The public API for the new platform currently omits essential APIs required to build an autonomous Wear OS client. While Toggl’s own first-party desktop and mobile apps connect via internal, undocumented endpoints, reverse-engineering private APIs would result in a brittle app that breaks every time Toggl pushes an update.

We believe in building stable, reliable tools. An unsupported private API is not a sustainable foundation for a watch app. Until Toggl opens complete public APIs for their new platform, independent Wear OS apps cannot reliably interface with new accounts.

What Does This Mean for You?

1. Existing / Legacy Toggl Track Users

ToggleWear continues to work exactly as before. Your tiles, complications, timer controls, and background sync are unaffected as long as your account has access to the classic Toggl Track backend.

2. New Toggl Users

New users who cannot access the legacy version at https://track.toggl.com/timer and are redirected to focus.toggl.com cannot use ToggleWear at this time (the Track button on your watch will remain disabled or inactive).

How to Check Your Account Type

Because Toggl's website simply refers to the platform as "Toggl", it can be hard to know which version your account uses. Here is a quick 5-second check:

1. In your browser, visit: https://track.toggl.com/timer (log in if asked).
2. Check the address bar in your browser:
   • If you stay on track.toggl.com: You have a supported legacy Toggl Track account. You can log into ToggleWear via Password or API Key.
   • If your URL redirects to focus.toggl.com: You have a new Toggl account. Because essential APIs are not available, third-party Wear OS integrations cannot connect.

Looking Ahead

Getting blindsided by platform decisions like this is one of the hardest parts of independent development, but we are committed to being 100% transparent with our community.

We are closely following Toggl’s developer announcements. The moment Toggl makes essential APIs available for their new platform, we will explore what is needed to bring ToggleWear to all users.

Thank you to everyone who has supported the project!