Thanks, my main problem was that /1/ did look *dirty*. The /v1/ is much better, ...

psadauskas · on July 17, 2010

No, please don't do this. Having a version string in the uri is bad. The version means nothing about the resource, and everything about the representation. Please see some of the links further down in the comments for a more detailed explanation.

qixxiq · on July 17, 2010

I've read through all the links, and whichever way I go its a compromise.

I'm choosing the /v1/ route because its a neat solution to the problem, it will work without serious issues and developers understand it easily.

Yes its not 110% REST, but I believe its the best solution to my problem. The fact that other major API's are taking the same route (Amazon,Twitter) just enforces the idea.