As others have said below and my own experience of running production APIs, the important thing is that you consider deprecation before you have deployed your f

As others have said below and my own experience of running production APIs, the important thing is that you consider deprecation before you have deployed your first API so that you know how you will eventually re-version things. Individual versioning of endpoints is hell on earth so no dice there. Future versions might be completely differently shaped, hosted on different platforms, written in different languages etc. These changes might be for good reasons but will be a pain for your customers (depending on whether you APIs are 1st-class netizens or some back-channel/low traffic thing), so setting the tone and habits early on, including considering how you expect customers to migrate to different requests/responses etc. saves you the awkward question later. You can't support version 1 forever in most cases.