If it is a public facing API than v1, v2
If it is a private facing API that likely is not to change you can skip versioning.
I have seen versioning with dates.
With GraphQL you don't require versioning in such regard which is the main selling point of GraphQL since versioning can come into play in iOS and Andriod development.
Some pass the version in the header request as Laurie suggests and others pass it in the JSON response.
Some people follow this standard which I bet has an opinion on versioning found somewhere within their website jsonapi.org/
If it is a public facing API than
v1,v2If it is a private facing API that likely is not to change you can skip versioning.
I have seen versioning with dates.
With GraphQL you don't require versioning in such regard which is the main selling point of GraphQL since versioning can come into play in iOS and Andriod development.
Some pass the version in the header request as Laurie suggests and others pass it in the JSON response.
Some people follow this standard which I bet has an opinion on versioning found somewhere within their website jsonapi.org/
Thank you so much for😊