We have exciting news! Toggl Track is introducing a long-requested feature: historical labor costs. We're making this change to help you better manage and understand your tracked time costs.

What's changing?​

Previously, labor costs were set using the labour_cost property. This method didn't maintain historical consistency - if you edited your labor cost, the change applied to all past tracked time. These costs were entered in cents (e.g., 1050 for $10.50).

Now, we're introducing a new way to handle labor costs with the labor_cost property. This updated approach ensures historical consistency, allowing you to specify when the new labor cost takes effect without altering past values. Costs are now entered in monetary units (e.g., 10.5 for $10.50).

Deprecation notice​

By 2024/08/31, we will deprecate the old labour_cost property. After this date, you won't be able to change labor costs using the cents-based method.

What you need to know​

1. Existing labor costs will be maintained: Your existing labor costs are safe and will be automatically migrated to the new feature. They will apply to all your past tracked time.

2. Flexible updates: When and if you decide to change labor costs, you can choose whether the new value should overwrite existing values or apply only from a specific date forward, similar to how rates are managed.

3. Seamless transition: If you use our applications, you don't need to do anything - the transition will be seamless.

4. Public API users: If you use our public API to set user labor costs, you'll need to update your code to refer to the new labor_cost property and use monetary decimal values instead of cents.

Example​

• Old method: labour_cost = 1050 (for $10.50)
• New Method: labor_cost = 10.5 (for $10.50)

In case you are wondering, we are renaming the property to "labor" to align with US standards.

We believe this update will make managing your labor costs easier and more accurate. If you have any questions or need assistance, please don't hesitate to reach out to our support team.

Thank you for being a valued Toggl Track user!

Back on 2023/08/14 we introduced a new authentication system that allows for both Track and Plan to have common user accounts.

In continuation of that effort we are deprecating more endpoints in favor of the common user account system.

Back on 2023/08/14 we introduced a new authentication system that allows for both Track and Plan to have common user accounts.

We are announcing the deprecation of Toggl Track's API v8. Calls to previous /api/v8/* endpoints, documented in the now archived [toggl_api_docs repository][toggl_api_docs], will cease to work in about six months. They should be replaced by their /api/v9/* counterparts documented in the [Docs][docs] section of this site.

This blog-like [Changes][changes] part of the documentation is where all the relevant changes made to the Toggl Track API will be published. Backwards-incompatible changes and deprecation notices will be informed in advance, allowing API clients to plan their migration accordingly.