7pace Timetracker’s API

Did you know that 7pace Timetracker and its resources are available not only over the Azure DevOps UI, but also via a set of APIs as well?

7pace has three sets of APIs:

• REST CRUD API
• Client API
• Reporting API

The REST CRUD API allows you to perform standard time tracking operations: tracking time, submitting time for approval, approving time, etc. Any operation that you perform from the UI is available through the REST CRUD subset of APIs. Although perhaps not as user-friendly as the UI, this method clears the path for integration with third-party tools and systems. Additional details on the REST CRUD are available here: REST CRUD API.

Secondly, we have the Client API. 7pace Timetracker can be installed on your Windows PC or a Mac in the form of a client application or downloadable desktop app that is synchronized with a DevOps organization over the network. Our desktop app offers a user-friendly UI with several options to track time. The Client API allows you to do the same thing with a REST call. Although this may not be something that you would do on a daily basis, it allows integration and communication with third-party tools and apps. You can find more information about the Client API and its resources here: Client API. Another option to address the same resources is provided through the SignalR interface at: Client (SignalR)

Thirdly, the most powerful and possibly the most frequently used API set is the Reporting API. The Reporting API allows you to get a combined output from both 7pace Timetracker’s own data as well as Azure DevOps’ proprietary data. The added value of 7pace Timetracker is that it allows you to not only track progress, but to calculate budgets, produce data for invoices to customers or even freelance engineers who work on multiple projects simultaneously. If a developer works freelance on three different projects, for example, and you need to calculate their work for a single month, you would need to combine data from different sources in addition to implementing a time variable.

This is where the 7pace Timetracker Reporting API would come into play. It uses the OData language to query data from 7pace Timetracker as well as the information from the Azure DevOps organization to allow for granular access to the data. So, with a well-structured query, you could get any data for any tracked work in any timeframe.

Although it’s important to note that certain queries could be “heavier” than others, the Reporting API still offers endless possibilities for tracking, calculation and quantification of developers’ efforts on a given project.For more information on the Reporting APIs resources, check out our OData Reporting API or watch our recorded webinar, below:

If you have any questions or feedback, please let us know in the comments, below!