Skip to content

Tag Archives: rest-versioning

Bookmarks and URI based versioning

Threads about how to version hypermedia (or REST) APIs are multitude. I certainly have made my opinion known in the past. That being said, the most common approach being used in the wild is putting a version number in the URI of the resources which are part of the API. For example, http://api.example.com/v1/products/42. That approach [...]

Posted 15 May 2012 † Peter Williams § Software Development ‡ Comments (0) ° Also tagged: ,

REST/HTTP Service Versioning (Response to Jean-Jacques Dubray)

Jean-Jacques Dubray takes issue with my approach of using content negotiation to manage service versioning in HTTP. I actually hesitate to respond to Mr. Dubray because the overall tone of his piece is rather off putting. On the other hand, he raises a couple of interesting questions which I have been really looking for and [...]

Posted 18 May 2008 † Peter Williams § Software Development ‡ Comments (15) ° Also tagged:

Versioning REST Web Services (Tricks and Tips)

In my previous post on this subject I described an approach to versioning the API of a REST/HTTP web service. This approach has significant advantages over the approach that is currently most common (i.e. embedding a version token in the URL). However, it does have some downsides. This post is an attempt to outline those [...]

Posted 13 May 2008 † Peter Williams § Software Development ‡ Comments (11) ° Also tagged: ,

Versioning REST Web Services

Managing changes to APIs is hard. That is no surprise to anyone who has ever maintained an API of any sort. Web services, being a special case of API, are susceptible to many of the difficulties around versioning as other types of APIs. For HTTP based REST style web services the combination of resources and [...]

Posted 11 May 2008 † Peter Williams § Software Development ‡ Comments (59) ° Also tagged: