Skip to main content
Google Play Connect uses a service account JSON key from Google Cloud. The same service account must be invited as a user in Play Console before it can access owned-app data.
Do not create or share a normal Google API key for this integration. The credential is the service account JSON file.

Required Google APIs

Enable these APIs in the Google Cloud project that will own the service account: Official references:

Android Publisher API

Service account setup for Google Play Developer API.

Developer Reporting API

Android vitals and quality reporting setup.

Create the Service Account JSON

  1. Open Google Cloud Console > IAM & Admin > Service Accounts.
  2. Choose the Google Cloud project connected to Play Console, or create a new project.
  3. Create a service account.
  4. Open the service account.
  5. Go to Keys.
  6. Create a new key.
  7. Select JSON.
  8. Download the JSON file.
You do not need to grant broad IAM roles inside Google Cloud for Play Console access. The important access control happens in Play Console after the service account is invited there.
If Google Cloud asks for a project IAM role during service account creation, a minimal viewer-style role is enough for creation flow. Play Console permissions decide which app data the API can access.

Invite the Service Account in Play Console

Open Play Console > Users and permissions, then invite the service account email from the JSON file. The email looks like:
Grant permissions based on the features the customer wants: For analytics dashboards, start with:
Add write permissions only when the customer wants Appeeky to reply to reviews or update releases/listings.

Connect Credentials

curl
The API verifies credentials before saving. A successful response means Google accepted the service account and the account can access at least basic Play Console app data.

Per-Request Credentials

Saved credentials are recommended. For testing, you can also pass credentials per request: Use saved credentials for production customers so background sync jobs can run without asking for headers on every request.

Check Status

curl
Example response:

Delete Credentials

curl
This removes the saved connection and deletes the encrypted credential from Appeeky.

Troubleshooting

Permission changes in Play Console can take time to propagate. If setup looks correct, wait a few minutes and retry.