Google Play Android Developer API

Name: Google Play Android Developer API API
Brand: Google Play Android Developer API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registryoauth2112 EndpointsREST

For Agents

Manage Google Play app releases, in-app products, subscriptions, and store listings via Edits. Useful for agents automating release pipelines, subscription management, and Play Console operations.

Quickstart

Get started with Google Play Android Developer API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"commit a google play edit and roll out a new release"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Play Android Developer API API.

Roll out new APK or AAB releases through Edits and commit them to Play

Manage in-app products and subscription offers with pricing and free trials

Validate and acknowledge subscription and product purchases server-side

Update store listings, screenshots, and graphic assets per locale

GET STARTED

Start building with Google Play Android Developer API API

Explore with Jentic

View OpenAPI Document

Use for: Upload a new app bundle and roll it out to 10 percent of production, Validate a subscription purchase token from the mobile client, Acknowledge an in-app product purchase, Promote a build from internal track to beta

Not supported: Does not handle device-side purchase flows, app build compilation, or device management — use for Google Play Console release, listing, and purchase validation operations only.

Use Cases

Patterns agents use Google Play Android Developer API API for, with concrete tasks.

★ Automated release pipeline

CI systems open a Play Edit, upload the AAB, attach the release notes, and commit the Edit on the production track at a staged rollout percentage. This replaces clicking through the Play Console for every release and lets the team ship multiple times a day with auditable history.

Open an Edit for package com.example.app, upload version-code 1042 AAB, set rollout 0.1 on production, and commit the Edit.

Subscription and purchase validation

Backend services validate subscription and one-time purchase tokens received from the mobile client to grant entitlements. The purchases endpoints return the purchase state, expiry, and renewal info so the backend can lock or unlock features based on real Play data rather than client claims.

Call purchases.subscriptions.get for token TOK_ABC on subscription premium_monthly and grant the user a 30-day entitlement if expiryTime is in the future.

Localized store listing updates

Marketing teams update titles, descriptions, screenshots, and feature graphics across many locales by opening an Edit and patching each listing. Committing the Edit publishes all locales atomically so the store does not show a half-updated state.

Open an Edit for com.example.app, patch the de-DE listing with a new shortDescription, and commit.

AI agent release operator via Jentic

An AI agent acting as a release manager opens Edits, uploads builds passed by CI, runs the Play pre-launch checks, and rolls out gradually. Through Jentic the agent searches for 'commit a play edit' and executes the operation without holding the underlying service account.

After CI publishes build 1042, open an Edit, upload the AAB, set rollout 0.05 on production, and commit. Post the new edit ID and rollout link to Slack.

Key Endpoints

112 endpoints — the google play android developer api lets app developers manage their google play presence programmatically.

METHOD

PATH

DESCRIPTION

POST

/androidpublisher/v3/applications/internalappsharing/{packageName}/artifacts/apk

Upload an APK for internal app sharing

POST

/androidpublisher/v3/applications/internalappsharing/{packageName}/artifacts/bundle

Upload an AAB for internal app sharing

GET

/androidpublisher/v3/applications/{packageName}/appRecoveries

List app recovery actions

POST

/androidpublisher/v3/applications/{packageName}/appRecoveries/{appRecoveryId}:deploy

Deploy an app recovery action

POST

/androidpublisher/v3/applications/{packageName}/dataSafety

Submit data safety declarations

GET

/androidpublisher/v3/applications/{packageName}/deviceTierConfigs

List device tier configurations

POST

/androidpublisher/v3/applications/internalappsharing/{packageName}/artifacts/apk

Upload an APK for internal app sharing

POST

/androidpublisher/v3/applications/internalappsharing/{packageName}/artifacts/bundle

Upload an AAB for internal app sharing

GET

/androidpublisher/v3/applications/{packageName}/appRecoveries

List app recovery actions

POST

/androidpublisher/v3/applications/{packageName}/appRecoveries/{appRecoveryId}:deploy

Deploy an app recovery action

POST

/androidpublisher/v3/applications/{packageName}/dataSafety

Submit data safety declarations

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Play Console service account credentials are stored encrypted in the Jentic vault. Agents call publisher operations through Jentic with scoped access tokens, never seeing the underlying JSON key or being able to leak it to a model context.

Intent-based discovery

Agents search Jentic with phrases like 'commit a play edit' or 'verify subscription token' and Jentic returns the matching publisher operation with its input schema, so the agent does not need to navigate the 112-endpoint surface manually.

Time to first call

Direct integration: 3-5 days to wire Edits, uploads, and purchase validation with proper retry handling. Through Jentic: under one hour to start running Edit, track, and purchase operations end-to-end.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Play EMM API

Distributes Play-published apps to managed Android devices via EMM.

Use Publisher to release the build; use the Play EMM API to push that build to a managed enterprise fleet.

Complementary

Android Management API

Pushes Play-published apps to enrolled devices through Android Management policies.

Use Publisher to ship to Play; use Android Management to enforce installation on enrolled corporate devices.

Complementary

App Engine Admin API

Hosts the backend services that validate Play purchases server-side.

Use App Engine for the entitlement service; use Publisher's purchases endpoints to validate the token before granting entitlement.

FAQs

Specific to using Google Play Android Developer API API through Jentic.

What authentication does the Google Play Android Developer API use?

OAuth 2.0 with a service account that has been linked to the Play Console developer account and granted the required permissions. Through Jentic the service account JSON is vaulted and only short-lived scoped tokens are used at call time.

Can I publish a new app version with this API?

Yes, but always through an Edit. Open an Edit with edits.insert, upload the AAB or APK with edits.bundles or edits.apks, set the desired track and rollout, then commit with edits.commit. Uncommitted Edits do not affect the live store listing.

What are the rate limits for the Google Play Android Developer API?

The API enforces a per-package daily quota and per-minute quota documented in the Play Console. Edit operations are cheap; bundle and APK uploads count more. Spread large bulk-listing updates across multiple Edits if you risk hitting the daily cap.

How do I validate a subscription purchase through Jentic?

Search Jentic for 'verify google play subscription', load the schema for purchases.subscriptions.get, and execute it with the packageName, subscriptionId, and purchase token. Grant entitlement only when paymentState and expiryTimeMillis confirm an active subscription.

Is the Google Play Android Developer API free?

The API is free for registered Play Console developer accounts. Costs are tied to the Play Developer account itself (one-time registration fee), not to API call volume.

Why do my changes not appear in the store after a successful API call?

Because the change is in an open Edit. Until you call edits.commit, modifications are staged. Confirm by listing the Edit and verifying the changes, then call commit. Failed commits typically mean policy or asset validation errors, which the response describes.