Google Play Console

Google Play Console: apps, releases, reviews, vitals, Play Integrity and Play Games

Connects by
Signing in with Google
Category
Developer tools
Part of
Google
Tools
210
ServiceKey
Google Play Consolegoogle-play

Connecting

Your client presses Connect on their link and approves on Google's own screen. Operate As never sees their password.

Check they're connected
curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "google-play"    ]  }]

Permissions

What the client readsPermission it asks for
See and manage your Google Play apps, reviews, releases and purchaseshttps://www.googleapis.com/auth/androidpublisher
See your Google Play apps' quality reportshttps://www.googleapis.com/auth/playdeveloperreporting
Check Play Integrity tokens for your appshttps://www.googleapis.com/auth/playintegrity
See and change your Play Games datahttps://www.googleapis.com/auth/games

Tools

Install Google Play Console's typed package for your language:

pip install operate-as-google-play
Run google-play.applications_data_safety
curl -X POST https://api.operate.as/v1/actions/google-play.applications_data_safety \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "package_name": "<package_name>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/google-play.applications_data_safety

Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://androidpublisher.googleapis.com/androidpublisher/v3. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../google-play/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Google refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer
HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Google access ended. Send them their link to reconnect."}
Your webhook receives
{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "google",    "services": [      "google-play"    ],    "reconnectUrl": "https://…"  }}