That's pretty much what the author has to say > Resource Versioning (URI-based) > Versioning specific resources by theirselves. > In the same example of /api

That's pretty much what the author has to say > Resource Versioning (URI-based) > Versioning specific resources by theirselves. > In the same example of /api/v1/companies and /api/v1/users, if companies changed substantially then maybe a /api/v2/companies is created, but /api/v1/users remains untouched. This makes upgrades easier for clients as they know where to focus their attention. If there is no v2 for users, they just keep on using the v1. > One problem with this approach is it looks nearly identical to global versioning on the outside, and isn’t. [goes on to list more problems, including MxN]