{"action":"opened","issue":{"url":"https://api.github.com/repos/json-api/json-api/issues/406","labels_url":"https://api.github.com/repos/json-api/json-api/issues/406/labels{/name}","comments_url":"https://api.github.com/repos/json-api/json-api/issues/406/comments","events_url":"https://api.github.com/repos/json-api/json-api/issues/406/events","html_url":"https://github.com/json-api/json-api/issues/406","id":60056037,"number":406,"title":"Clarify the versioning strategy for APIs","user":{"login":"extesy","id":65872,"avatar_url":"https://avatars.githubusercontent.com/u/65872?v=3","gravatar_id":"","url":"https://api.github.com/users/extesy","html_url":"https://github.com/extesy","followers_url":"https://api.github.com/users/extesy/followers","following_url":"https://api.github.com/users/extesy/following{/other_user}","gists_url":"https://api.github.com/users/extesy/gists{/gist_id}","starred_url":"https://api.github.com/users/extesy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/extesy/subscriptions","organizations_url":"https://api.github.com/users/extesy/orgs","repos_url":"https://api.github.com/users/extesy/repos","events_url":"https://api.github.com/users/extesy/events{/privacy}","received_events_url":"https://api.github.com/users/extesy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-06T03:55:29Z","updated_at":"2015-03-06T03:55:29Z","closed_at":null,"body":"I think it would be useful to standardize the approach to versioning the API. For example, when I want to change the request or response format for some API endpoint, which is backwards incompatible. How should the client tell which API version to use?\r\n\r\nThere are many different approaches to this: put version in url like /api/1/action or /api/v1/action or in the header, like \"Content-Type: application/vnd.company+json.v1\" or \"X-API-Version: 1\".\r\n\r\nHow about explicitly including the strategy to versioning API in this specification?"}}