REST API Versioning

by XDK 19. July 2019 18:48

Explanation:

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.0
Query parameter: GET {url}/{organization}/_apis/{area}/{resource}?api-version=1.

Supported versions

Product 1.0 2.0 3.0 4.0 5.0
Azure DevOps Services 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 - - -

Note : Once a preview API is deactivated, requests that specify a -preview version will be rejected (for example, 1.0-preview.1, 1.0-preview.2).

 

Tags:

Azure Native DevOps | REST APIs | Azure DevOps on-premises

About the author

My name is Xavier Dilip Kumar Jayaraj having 16+ years of IT experience which includes solid experience and depth Knowledge in Application Life Cycle Management, Configuration Management, Implementation and Support using TFS on-premises and Azure DevOps. I have invested in gaining DevOps knowledege to expertise with Cloud Computing providers namely Microsoft Azure and Amazon Web Services in recent years. I am very positive to learn and adapt emerging technologies to client’s environment.

Microsoft Certified: Azure Administrator Associate

Microsoft Certified: Azure DevOps Engineer Expert

DevOps Engineer Certificate Program | Transcript 

OTP-AWSD5: AWS IoT: Developing and Deploying an Internet of Things

[PCEP-30-01] PCEP – Certified Entry-Level Python Programmer

Quotes I Like

"Failure will never overtake me if my determination to succeed is strong enough."  - Dr. APJ. Abdul Kalam

"Always be yourself, express yourself, have faith in yourself, do not go out and look for a successful personality and duplicate it." - Bruce Lee

"Technology is just a tool. In terms of getting the kids working together and motivating them, the teacher is the most important." - Bill Gates

"Innovation distinguishes between a leader and a follower." - Steve Jobs

CategoryList

Disclaimer

The information provided here is based on my expreriences, troubleshooting and online/offline findings. It can be used as is on your own risk without any warranties and I impose no rights.