df2fa823fd
As described in play-store-api code [1] recenlty google introduced a Time To Live to each auth token, which caused them to expire in a matter of seconds. Moreover, in order to retrieve a long-ttl token, a second auth request now is needed, sending the Master Token returned from the first request. This 'second round' request will return the actual authSubToken. Another addition is that the code now return response's text for some generic errors, in order to help debugging those problems. |
||
|---|---|---|
| Documentation | ||
| gpapi | ||
| .gitignore | ||
| .travis.yml | ||
| googleplay.proto | ||
| LICENSE.md | ||
| obb_download_test.py | ||
| README.md | ||
| setup.cfg | ||
| setup.py | ||
| test.py | ||
Google play python API 
This project contains an unofficial API for google play interactions. The code mainly comes from GooglePlayAPI project which is not maintained anymore. The code was updated with some important changes:
- ac2dm authentication with checkin and device info upload
- updated search and download calls
- using headers of a Nexus 6P. Add you own device under
device.propertiesfile
Usage
Check the test.py module for a simple example.
An important note about login function:
def login(self, email=None, password=None, gsfId=None, authSubToken=None)
for first time logins, you should only provide email and password. The module will take care of initalizing the api,upload device information to the google account you supplied, and retrieving a Google Service Framework ID (which, from now on, will be the android ID of a device).
For the next logins you should save the gsfId and the authSubToken, and provide them as parameters to the login function. If you login again with email and password only, this is the equivalent of re-initalizing your android device with a google account.
Documentation
For some documentation about the google play API check out the relative folder.