AppScreenshots DocsSet up Google Play API credentials
Enable the API, create a service-account JSON key and grant the correct Play Console access.
Use a service account that you control. This is a JSON credential file, not a simple API key. Keep it on a trusted device.
1. Enable the API
In Google Cloud, select a project and enable Google Play Android Developer API in the API Library.
2. Create a service account and key
The person creating the key needs permission to manage that service account's keys, such as the Service Account Key Admin role. This is permission for the operator, not a Cloud project role that Store Sync needs you to grant to the service account. If the controls are missing, ask your project administrator to check your access. Google's required roles.
Open IAM & Admin → Service Accounts, create an account and record its email. Play access does not require granting that account Cloud project Owner or Editor.
Open the account's Keys tab, choose Add key → Create new key → JSON, and save the downloaded file. If organizational policy blocks key creation, contact the administrator; do not bypass that policy. See Google's key instructions.
3. Authorize it in Play Console
Open Play Console → Users and permissions, invite the service-account email, and select the relevant apps. Grant the app-information read access and Manage store presence permission needed for listing operations. Account-level permissions cover a wider app scope; use selected-app access where possible.
Draft apps can require additional draft-app permissions. Inspect the actual permission description before granting it. Do not grant billing, finance or release-management permissions for this listing workflow. Google API setup and Play permissions.
4. Import and verify
Open Google settings in Store Sync. Import the JSON file or paste its complete contents into the service-account JSON field, according to the controls available in your version. Allow the requested official Google API hosts, then verify and save.
| JSON field | Plugin value |
|---|---|
| client_email | Service-account email |
| private_key | Signing private key |
| project_id | Cloud project ID, when present |
Do not substitute the developer account ID, app package name or an OAuth client secret.
Credential verification checks authentication. Preflight separately checks the selected package and listing access. It creates and discards a temporary edit; it is not only a GET request.
Confirm the operation
Saving commits the edit. Commit can trigger review or publishing. Review the plugin confirmation and the remote console, especially after a timeout. A successful API commit does not mean review approval.
Troubleshoot and revoke
For 401, check the key and device time. For 403 or an unavailable app, check API enablement, the invited email, Play permissions and package scope. Allow for permission propagation.
To revoke a key, delete it from the service account's Keys tab. Remove or narrow Play Console access if no longer needed. Local deletion in Store Sync does not perform these actions.
Reviewed against plugin fields and linked Google documentation on 2026-09-17. Back to Store Sync.