How easy did you find this article?
Many third party plugins are using version 3 of the API. Should you use a plugin that does not support version 3 you will need to contact the maintainer. If we detect that your program is still using version 1 and version 2 endpoints, you will start seeing warnings from the Google Play Console from mid-May.
If you currently use version 1 of the API, then you may need to join your API project to the Google Console before switching to version 3. Learn more about this process.
We hope you are looking forward to your feedback to help us improve the publishing encounter and benefit from the features of this Google Play Developer Publishing API.
Should you use the Google Play API client libraries (available for Java, Python, along with other popular languages), we recommend upgrading to their latest versions, which support version 3 of the API. Changing the version of the client library should be all that is necessary. But, you might also have to update particular code references to the edition of the API in use – see examples in our samples repository.
For version 1 users
Besides these new features, version 3 supports all the functionality of previous versions, simplifying and improving how you handle workflows. Beginning December 1, 2019, versions 1 and 2 of those Google Play Developer API will no more be available so you have to update to version 3 ahead of the season.
Migrating to model 3
The Google Play Developer API allows you to automate your in-app billing and app distribution workflows. In Google I/O’18, we introduced variation 3 of the API, which lets you transactionally start, handle, and stop staged releases on all tracks, through manufacturing, start testing, closed testing (including the newest further testing tracks), and internal testing.
Updating from versions 1 and 2 to the Most Recent version 3