On this page, we will talk about one of the upcoming changes for the VK API platform. To see the list of all the previous and upcoming changes, click here.
1. How it works now
2. What is going to change
3. How to migrate to version 5.0
Estimated date of release: May 27, 2019
From version to version in our API, we change names of the fields, their data types, and object structure. In order to properly process the API methods response data in your application, it’s important to know beforehand which data in which format will be returned from the server. By specifying the version number in your request, you are telling the server which data format you are expecting to receive in response.
In 2014, a global API update was launched, which affected almost all methods, objects and their fields. For a long time, we couldn't deprecate old versions from use, because it's important for us to support the compatibility of the platform with old applications, which many people still use. But supporting them puts more and more restrictions on advancing the platform, which is why we made a decision to deprecate all versions before 5.0
After version deprecation many developers used older API versions in their applications to maintain compatibility. But major versions 3.0
are outdated, they don't support many object types, and the response format of most of the methods is completely different from what you see in documentation examples.
All the calls to API with the 3.0
version number specified will no longer be supported. In this case, the server will return an error as a response.
Almost all object structure and field names in version 5.0 are different from those that are used in 3.0 and 4.0. You will have to update your code according to our documentation. The most important changes to note while migrating to 5.0 are listed here
Here is the list of all version changes: https://vk.com/dev/versions