Announcing the new Toggl Track API, v9!

Pink lightbulbs lined up in slanted manner. One of the lightbulbs is yellow and bright.

The Toggl Track API got better—better documentation, better performance and stability, and better support for new features. Say goodbye to v8 and switch to the current v9 to take full advantage of all these new advantages.

What’s so great about the new API?

• More developer-friendly documentation

The new API (v9) features much better documentation, so that it’s easier to find what you need. Thanks to a thorough refactoring, our API documentation is cleaner and more readable than ever before.

It’s also got a new home! Track API v8 was hosted on Github, but you can find v9 on our website at Pretty!

• Better support

Chances are, the improved clarity and design of v9 means you won’t need help. But when you do need it, it’ll be easier for us to find problems and suggest solutions.

• Better performance and stability

The code might have changed, but our functionality has not—unless you count improved performance and reliability. It’s not one big thing, but the little things: fewer bugs, more consistency.

• More innovative features from us

The new API enables more innovative features, such as the ability to add time entries for other users. We call the feature add time for team. And now it’s also available on our API v9 for anyone on a Premium or Enterprise plan.

The new API also features Organizations, an extra layer of administrative control above the Workspace level that allows you to manage settings and users for multiple workspaces.

We’re always attuned to feature requests from our users, and v9 will allow us to deliver on these new features more quickly.

Our company is scaling fast and v9 is the engine that will enable us to scale our product to support more users, to speed up our infrastructure, and empower our developers.

What does this mean for you?

We’re phasing out v8 within the next six months. To ensure that your API implementations work with the latest Track features, including multiple workspaces as well as your own custom or third-party integrations, we encourage you to start the migration sooner rather than later.

To get started, head over to

Keep in mind that replacing the endpoints is not enough. Please make sure you follow the directions in the documentation to check how the new endpoints work.

Feedback, general or specific? Just contact us at

April 12, 2022