Technical Guide: Connecting Google Play Console API via Google Cloud Service Account

In recent updates to the Google Play Console, the API Access interface has been restructured. Instead of a dedicated menu, developers now manage access through a Service Account created in the Google Cloud Platform (GCP). This guide provides a step-by-step technical workflow to set up this connection for automated tasks like .aab (Android App Bundle) uploads.

This guide provides detailed instructions on connecting to the Google Play Console API via a Service Account from Google Cloud. It addresses issues such as not finding the API Access entry, guides you on assigning Service Account User permissions, and outlines the steps for automatically uploading .aab files for developers.

• Platform: Google Play Console & Google Cloud Platform.
• Goal: Automated app publishing (.aab upload).
• Authentication: JSON Key (Service Account).
• Updated: 2026.

1. Why Use a Service Account?

A Service Account acts as a “machine user,” allowing CI/CD tools (e.g., Fastlane, GitHub Actions) to interact with the Google Play API securely. This eliminates the need for manual 2FA (Two-Factor Authentication) and enables a fully automated deployment pipeline.

2. Step-by-Step Technical Setup

Step 1: Create a Service Account on Google Cloud Console

1. Navigate to the Google Cloud Console.

2. Select the Project associated with your application.

3. Go to IAM & Admin > Service Accounts.

4. Click Create Service Account:

   • Service account name: Use a descriptive name (e.g., play-console-uploader).

   • Service account ID: This will be generated automatically. Note the email address (formatted as @project-id.iam.gserviceaccount.com).

5. In the Permissions step, assign the Service Account User or Editor role.

6. In the Principals with access step, you may leave this blank and click Done.

Step 2: Generate and Download the JSON Key

1. In the Service Accounts list, click on the email address you just created.

2. Switch to the Keys tab.

3. Click Add Key > Create new key.

4. Select JSON as the key type and download the file.

   Security Note: This file contains sensitive credentials. Never commit this file to public repositories or share it via insecure channels.

Step 3: Link the Service Account to Google Play Console

1. Log in to the Google Play Console.

2. Navigate to Users and permissions.

3. Click Invite new users.

4. Paste the Service Account email address copied from Step 1.

5. Under the App permissions tab, select your specific app and grant the following:

   • Manage tracks: Required for uploading builds to Internal, Alpha, or Beta tracks.

   • Manage production releases: Required for promoting builds to Production.

   • Manage store presence: Required if your automation updates store metadata or screenshots.

6. Click Invite user. The account status will immediately show as Active without requiring manual confirmation.

3. Technical Q&A

Q1: I cannot find the “API Access” section in Play Console as described in older documentation.

• Answer: Google has integrated this into Users and permissions. Inviting the GCP Service Account as a user to your Play Console automatically enables API access for that account.

Q2: My Google Play Developer account is different from my Google Cloud account. Is this an issue?

• Answer: No. You can create the Service Account in any Google Cloud project and then “invite” that email address into your Google Play Developer Console. The systems link via the Service Account email, regardless of the primary owner.

Q3: I sent the invitation from Play Console, but I don’t see a notification to “Accept” it in Google Cloud.

• Answer: Service Accounts are non-human entities and do not have an inbox. Unlike a standard user invitation, once you click “Invite” in the Play Console, the link is established instantly. No manual acceptance is required.

Q4: Which roles are required to upload an .aab file?

• Answer:

  • On Google Cloud: Assign the Service Account User role.

  • On Play Console: Ensure the account has Manage tracks (for test builds) and/or Manage production releases (for live builds).

4. Verification

Once configured, use your JSON Key file with your deployment tool (e.g., fastlane). A successful connection will return a 200 OK status code, confirming that your automated release pipeline is operational.

Keyword: upload .aab via API, Google Play Developer API setup 2026, link Google Cloud to Play Console.