API 2.1 Migration FAQ

API v2.1 was deprecated more than four years ago (see API Important Information) and now, the process of finally retiring it is ongoing. Once this API v2.1 is retired, you can no longer obtain data via this version.

This article provides answers to the questions you may have and provides guidance with the migration process to the updated and supported API versions.

On this page: 1 Why is 7pace retiring API v2.1? 2 When will API v2.1 be shut down? 3 How can I tell if I am sending API v2.1 requests? 4 What API should I use as replacement? 5 Will API v2.1 be shut down for on-prem too? 6 What are the differences?

On this page: 1 Why is 7pace retiring API v2.1? 2 When will API v2.1 be shut down? 3 How can I tell if I am sending API v2.1 requests? 4 What API should I use as replacement? 5 Will API v2.1 be shut down for on-prem too? 6 What are the differences?

Why is 7pace retiring API v2.1?

Software is constantly evolving and so are its APIs. The TimeExport endpoint found in API v2.1 does not support pagination and includes all attributes in the response by default. This makes the API less than effective, which leads to occasional performance issues.

7pace provides more recent APIs that can provide the same data, but in an optimized way.

When will API v2.1 be shut down?

API v2.1 has been retired - stopped serving requests - on 1st December, 2023. Optional prolongation period of limited length (several months) can be requested by an e-mail sent to support@7pace.com.

How can I tell if I am sending API v2.1 requests?

The API endpoint and version are a part of URL that your application calls, and can be seen in the example below.

https://yourcompany.timehub.7pace.com/api/odata/TimeExport(StartDate='2019-06-14',EndDate='2023-06-14',PopulateTopParentColumns=null,GroupTimeByDateByUser=null,IncludeBillable=null)?api-version=2.1

What API should I use as replacement?

The safest way is to use the newest stable version of the API that is listed in our API documentation. Currently (Q3/2022) it is 3.2.

Note that the TimeExport endpoint no longer exists in the new APIs, you will therefore have to call different endpoints with a different structure of requests. We recommend reading the following documentation:

Choosing a specific endpoint of API v3.2 depends on your needs. The most frequent cases are listed below; the rest of the endpoints are described in the mentioned user guides.

workLogsOnly endpoint is the most effective if you only need to obtain worklogs.
Choose workLogsWorkItems endpoint if you also need to obtain workitems (and, optionally, information about their parent item).

Will API v2.1 be shut down for on-prem too?

If you run Azure DevOps and Timetracker on your own servers, you can continue using API v2.1. However, there is no guarantee that future versions of Timetracker will work with this API properly, and, troubleshooting support and bug fixing for API v2.1 are not available.

What are the differences?

API version 2.1	API version 3.0 and higher	Comment
Limited filtering (start date, end date, flags)	Advanced filtering of records (by any attribute)	We recommend obtaining only updated records for a certain time period using filtering by EditedTimestamp - see Incremental refresh guide.
Not paginated	Paginated	Pagination is handled via `@odata.nextLink` property. Certain tools like Excel or Power BI handle the pagination automatically. You have to choose Odata feed as data source.
API version in parameters Example: `?api-version=2.1`	API version in the base URL Example: https://url.timehub.7pace.com/api/odata/v3.2/
Returns all object attributes (properties) by default	Explicit selection of attributes is enforced due to a newer OData standard	See the respective documentation.
Single `TimeExport` endpoint to rule them all	Multiple endpoints suited for different use cases	See the preceding sections for more information about endpoints.