| title | REST API Versioning for Azure DevOps |
|---|---|
| description | Learn about the importance of versioning in REST APIs and explore guidance on implementing versioning in your projects in Azure DevOps. |
| ms.assetid | 5fc6efd4-9947-40f2-b4f6-9695a24de87c |
| ms.subservice | azure-devops-ecosystem |
| ms.topic | concept-article |
| ms.custom | engagement-fy23 |
| monikerRange | <= azure-devops |
| ms.author | chcomley |
| author | chcomley |
| ms.date | 04/10/2025 |
[!INCLUDE version-lt-eq-azure-devops]
Using versioned REST APIs, you can ensure that your projects are scalable and maintainable over time, and that your applications and services continue to work as APIs evolve.
-
API version must be specified with every request.
-
API versions are in the format
{major}.{minor}[-{stage}[.{resource-version}]]. For example:1.0,1.1,1.2-preview,2.0 -
While an API is in preview, you can specify a precise version of a particular revision of the API when needed. For example:
1.0-preview.1,1.0-preview.2 -
After an API is released (
1.0, for example), its preview version (1.0-preview) is deprecated and can be deactivated after 12 weeks. -
During this time, you should upgrade to the released version of the API. Once a preview API is deactivated, requests that specify a
-previewversion get rejected.
The API version can be specified either in the header of the HTTP request or as a URL query parameter:
HTTP request header:
Accept: application/json;api-version=1.0Uri query parameter:
[scheme"://"][host[':'port]]"/v" major-version '/'namespace '/'resource ('/'resource)* '?' query
i.e. GET https://dev.azure.com/v1.0/{organization}/_apis/{area}/{resource}?some-query=1000
Note
All supported Rest APIs are documented in the Azure DevOps Services REST API Reference.
Team Foundation Server was renamed Azure DevOps Server in 2019.
| Product | 1.0 | 2.0 | 3.0 | 4.0 | 5.0 | 6.0 | 7.0 |
|---|---|---|---|---|---|---|---|
| Azure DevOps Services | X | X | X | X | X | X | X |
| Azure DevOps Server 2022 | X | X | X | X | X | X | X |
| Azure DevOps Server 2020 | X | X | X | X | X | X | - |
| Azure DevOps Server 2019 | X | X | X | X | X | - | - |
| Team Foundation Server 2018 | X | X | X | X | - | - | - |
| Team Foundation Server 2017 | X | X | X | - | - | - | - |
| Team Foundation Server 2015 | X | X | - | - | - | - | - |
Major API version releases align with Team Foundation Server RTM releases. For example, the 3.0 API set was introduced with Team Foundation Server 2017.
A few undocumented version 1.0 APIs existed in Team Foundation Server 2013, but aren't supported.