Google Play Connect Overview

Google Play Connect is for apps you own in Google Play Console. It is the Google Play counterpart to App Store Connect: customers connect their own Play Console account, then Appeeky can read private owner data and power dashboards, reviews workflows, vitals monitoring, and publishing tools. Public ASO endpoints do not need this setup. Use platform=google on the public endpoints when you want public app metadata, screenshots, keyword ranks, and competitor intelligence for any Play Store app.

Google Play Connect uses a Google Cloud service account JSON key. It does not use a normal Google API key. The service account must also be invited in Play Console > Users and permissions.

How It Works

Customer Google Cloud project
  -> service account JSON
  -> Play Console user invite + permissions
  -> Appeeky /v1/connect/google-play/credentials
  -> Appeeky stores encrypted credentials
  -> API and scheduled sync jobs read Play Console data

Appeeky securely stores the service account credential encrypted at rest. Non-sensitive connection details such as the service account email, default package name, reports bucket, and sync status are used to show connection state and run scheduled syncs.

What You Can Access

Area	What it covers	Docs
Credentials	Service account JSON, Play Console permissions, saved connection status	Credentials & Setup
Report exports	GCS bucket, monthly CSV reports, object listing and downloads	Report Exports
Analytics	Dashboard rollups for installs, first opens, MAU, ratings, crashes, store conversion, search terms	Analytics
Reviews & Vitals	List reviews, reply to reviews, query Android vitals, anomalies	Reviews & Vitals
Publishing	Tracks, releases, store listing metadata, subscriptions, one-time products	Publishing & Monetization
API Reference	Full endpoint list and request surface	API Reference

Customer Setup Flow

Create or choose a Google Cloud project.
Enable the Google Play APIs.
Create a service account JSON key.
Invite the service account email in Play Console.
Grant the permissions needed for the features the customer wants.
Find the Play Console reports bucket if analytics imports are needed.
Connect credentials through Appeeky.
Verify app access, report access, and analytics import.

Start with Credentials & Setup. If the customer only wants dashboard analytics, then continue with Report Exports and Analytics.

Recommended Minimum Permissions

Use case	Minimum permission set
Analytics dashboard	Global `View app information and download bulk reports`, plus Android vitals access
Reviews dashboard	Review read permission
Reply to reviews	Review reply permission
Release visibility	Release/track read permission
Release updates	Release management permission
Store listing updates	Store listing management permission
IAP/subscription visibility	Monetization product read permission
Financial reports	Global `View financial data`

For bulk report exports, Google requires account-level/global permissions. App-scoped access can be enough for some Play APIs, but it is usually not enough for the private GCS report bucket.

Typical Workflow

1. Connect credentials

POST /v1/connect/google-play/credentials

See Credentials & Setup.

2. List owned apps

GET /v1/connect/google-play/apps

Use this to confirm that the service account can see the customer’s Play Console apps.

3. Verify report access

GET /v1/connect/google-play/reports/objects?prefix=stats/installs/

If this fails with storage.objects.list denied, the service account is authenticated but does not have bulk report access. See Report Exports.

4. Import analytics

POST /v1/connect/google-play/analytics/import-reports
POST /v1/connect/google-play/apps/:packageName/analytics/vitals-sync

Dashboard reads should use the synced analytics endpoints:

GET /v1/connect/google-play/apps/:packageName/analytics
GET /v1/connect/google-play/apps/:packageName/analytics/search-terms
GET /v1/connect/google-play/apps/:packageName/analytics/sources

Endpoint Families

Family	Endpoints
Credentials	`POST /credentials`, `GET /credentials/status`, `DELETE /credentials`
Apps	`GET /apps`
Reviews	`GET /apps/:packageName/reviews`, `POST /apps/:packageName/reviews/:reviewId/reply`
Vitals	`GET /apps/:packageName/vitals/:metricSet`, `POST /apps/:packageName/vitals/:metricSet/query`, `GET /apps/:packageName/anomalies`
Reports	`GET /reports/objects`, `GET /reports/object`, `GET /reports/download`
Analytics	`POST /analytics/import-report`, `POST /analytics/import-reports`, `GET /analytics`, `GET /apps/:packageName/analytics`
Publishing	Tracks, releases, localized listings
Monetization	Subscriptions and one-time products

For the complete endpoint list, see Google Play Console API Reference.

Getting Started

Apps

My Data - Appeeky Web

Keywords

ASO Tools

AI Visibility

Search & Discovery

Market Intelligence

RevenueCat

App Store Connect

Google Play Console

Apple Search Ads

Growth Channels

Reference

How It Works

What You Can Access

Customer Setup Flow

Recommended Minimum Permissions

Typical Workflow

1. Connect credentials

2. List owned apps

3. Verify report access

4. Import analytics

Endpoint Families

​How It Works

​What You Can Access

​Customer Setup Flow

​Recommended Minimum Permissions

​Typical Workflow

​1. Connect credentials

​2. List owned apps

​3. Verify report access

​4. Import analytics

​Endpoint Families

How It Works

What You Can Access

Customer Setup Flow

Recommended Minimum Permissions

Typical Workflow

1. Connect credentials

2. List owned apps

3. Verify report access

4. Import analytics

Endpoint Families