It's very common to specify the version of REST APIs in the URL, specifically at the beginning of path, i.e. something like:
POST /api/v1/accounts GET /api/v1/accounts/details
However, I haven't seen any design where the version is associated with each API. In other words, we maintain the version of each API separately. i.e.:
POST /api/accounts/v2 GET /api/accounts/details/v3
Using this approach we increment the API version of the specific API when breaking change is needed, no need to increment the version of the whole APIs.
What are the drawbacks of using this style instead of the common style?