Deploy an APK or AAB file to a Play Store track.

Two-step: call with confirm=False first, show the returned preview to the user, and only call again with confirm=True and the preview's confirmation_token once they have approved it.

Deploy an APK or AAB file with multi-language release notes.

Promote a release from one track to another.

Two-step: preview first, then confirm with the preview's token.

Get release status for all tracks of an app.

Halt a staged rollout. Takes effect immediately, no confirmation needed.

Deliberately NOT behind the confirmation gate. Halting is the one operation that makes things safer, and demanding a second round-trip during an incident is itself the failure mode. It is still written to the audit log.

Update the rollout percentage for a staged release.

Use this to increase or decrease the percentage of users receiving an update. Set to 100 to complete the rollout. Two-step: preview, then confirm.

Get app details including title, description, and developer info.

Get recent reviews for an app.

Reply to a user review.

Get a single user review by its ID.

List all subscription products for an app.

Get the status of a subscription purchase.

List voided purchases (refunds, chargebacks).

Get the status of an in-app product purchase.

Acknowledge an in-app product purchase.

Purchases not acknowledged within 3 days are automatically refunded.

Consume an in-app product purchase (for consumable products).

Marks the product as consumed so the user can purchase it again.

Refund an order, optionally revoking the user's entitlement.

Cancel a subscription purchase.

Defer a subscription purchase's next renewal.

Revoke (refund) a subscription purchase.

Get the status of an in-app product purchase using the v2 API.

Unlike get_product_purchase, this identifies the purchase by token alone (no product ID) and returns line items and acknowledgement state.

List all in-app products for an app.

Get details of a specific in-app product.

Create a new in-app product in the catalog.

Disabled in read-only mode.

Update (replace) an existing in-app product.

Disabled in read-only mode.

Partially update an existing in-app product.

Disabled in read-only mode.

Delete an in-app product from the catalog.

Disabled in read-only mode.

Get details for multiple in-app products at once.

Delete multiple in-app products in a single operation.

Disabled in read-only mode.

Get details of a specific one-time product.

List all one-time products for an app.

Get details for multiple one-time products at once.

Create or update a one-time product (patch is create-or-update).

Disabled in read-only mode.

Delete a one-time product from the catalog.

Disabled in read-only mode.

Update multiple one-time products in a single operation.

Disabled in read-only mode.

Delete multiple one-time products in a single operation.

Disabled in read-only mode.

Delete multiple purchase options from a one-time product in a single operation.

Disabled in read-only mode.

Activate or deactivate multiple purchase options in a single operation.

Disabled in read-only mode.

List all offers for a one-time product purchase option.

Get details for multiple one-time product offers at once.

Activate a one-time product offer, making it available to eligible buyers.

Disabled in read-only mode.

Deactivate a one-time product offer, making it unavailable to new buyers.

Disabled in read-only mode.

Cancel a one-time product offer (e.g. a pre-order offer).

Disabled in read-only mode.

Create or update multiple one-time product offers in a single operation.

Disabled in read-only mode.

Activate, deactivate or cancel multiple one-time product offers in a single operation.

Disabled in read-only mode.

Delete multiple one-time product offers in a single operation.

Disabled in read-only mode.

Get details of a specific subscription product.

Create a new subscription product in the catalog.

Disabled in read-only mode.

Partially update an existing subscription product.

Disabled in read-only mode.

Delete a subscription product from the catalog.

Disabled in read-only mode.

Get details for multiple subscription products at once.

Update multiple subscription products in a single operation.

Disabled in read-only mode.

Activate a subscription base plan, making it available to new subscribers.

Disabled in read-only mode.

Deactivate a subscription base plan, making it unavailable to new subscribers.

Existing subscribers keep their subscription. Disabled in read-only mode.

Delete a subscription base plan.

Only inactive base plans with no active subscribers can be deleted. Disabled in read-only mode.

Migrate subscribers to the current base plan prices.

Disabled in read-only mode.

Migrate prices for multiple base plans in a single operation.

Disabled in read-only mode.

Activate or deactivate multiple base plans in a single operation.

Disabled in read-only mode.

Get details of a specific subscription offer.

List all offers for a subscription base plan.

Create a new subscription offer.

Disabled in read-only mode.

Partially update an existing subscription offer.

Disabled in read-only mode.

Activate a subscription offer, making it available to eligible subscribers.

Disabled in read-only mode.

Deactivate a subscription offer, making it unavailable to new subscribers.

Disabled in read-only mode.

Delete a subscription offer.

Only inactive offers with no active subscribers can be deleted. Disabled in read-only mode.

Get details for multiple subscription offers in a single operation.

Update multiple subscription offers in a single operation.

Disabled in read-only mode.

Activate or deactivate multiple subscription offers in a single operation.

Disabled in read-only mode.

Get store listing for a specific language.

Update store listing for a specific language.

List all store listings for all languages.

Get testers for a specific testing track.

Update testers for a specific testing track.

Get detailed order/transaction information.

Get detailed information for multiple orders at once.

Get an external (alternative billing) transaction.

Create an external (alternative billing) transaction.

Refund an external (alternative billing) transaction.

Get a device tier config.

List all device tier configs for an app.

Create a new device tier config.

Disabled in read-only mode.

List users with access to a developer account.

Grant a user access to a developer account.

Disabled in read-only mode.

Update a user's account access.

Disabled in read-only mode.

Remove a user's access to a developer account.

Disabled in read-only mode.

Grant a user app-level access.

Disabled in read-only mode.

Update a user's app-level access.

Disabled in read-only mode.

Remove a user's app-level access.

Disabled in read-only mode.

Write the data safety labels declaration of an app.

Supply EITHER csv_path (preferred) OR safety_labels, not both.

There is no API to read the current declaration back, so the CSV can only come from Play Console > App content > Data safety > Export to CSV, and that exported file is the only thing that could ever undo this write. Export one before you start.

A csv_path is checked before anything is sent, and the file is read again on the confirm leg — so the approval is bound to the answers, not to the path.

Disabled in read-only mode. Two-step: preview, then confirm.

List all app recovery actions for an app version.

Create a draft app recovery action.

Disabled in read-only mode.

Deploy an app recovery action to users.

Disabled in read-only mode.

Cancel an app recovery action.

Disabled in read-only mode.

Add targeting to an app recovery action.

Disabled in read-only mode.

List the APKs Google Play generated from an app bundle version.

Returns one entry per downloadable generated APK (split, standalone, universal, asset pack slice, or recovery), each with a download ID that can be passed to download_generated_apk.

Download a single generated APK to a local file.

Get a previously created system APK variant.

List previously created system APK variants for an app bundle version.

Create a system APK variant from an uploaded app bundle.

Disabled in read-only mode.

Download a previously created system APK variant to a local file.

Get APK expansion file information.

Expansion files are used for large apps (especially games) that exceed the 100MB APK size limit.

List the APKs currently uploaded for an app.

List the Android App Bundles currently uploaded for an app.

Upload an APK to a new edit and commit it.

Disabled in read-only mode.

Upload an Android App Bundle (.aab) to a new edit and commit it.

Disabled in read-only mode.

Upload a deobfuscation (ProGuard mapping or native symbols) file.

Disabled in read-only mode.

Upload an APK expansion file (OBB) to a new edit and commit it.

Disabled in read-only mode.

List the store-listing images for a language and image type.

Upload a store-listing image (PNG or JPEG) to a new edit and commit it.

Disabled in read-only mode.

Delete a single store-listing image by ID and commit the edit.

Disabled in read-only mode.

Delete all store-listing images for a language and image type; commit the edit.

Disabled in read-only mode. Two-step: preview, then confirm.

Validate package name format before using it in other operations.

Validate track name before using it in deployment operations.

Validate store listing text lengths before updating.

Deploy an app to multiple tracks in a single operation.

This is useful for deploying to internal and alpha tracks simultaneously, or for promoting to multiple testing tracks at once.

Upload an APK to internal app sharing.

Disabled in read-only mode.

Upload an app bundle (.aab) to internal app sharing.

Disabled in read-only mode.

List every app the service account can see through the Reporting API.

The Publisher API has no "list my apps" endpoint, so this is the only way to enumerate a portfolio from a service account.

List the vitals metric sets this server can query.

Returns: Each metric set's short key (use it as the metric_set argument), the underlying Play resource suffix, and a human-readable label

List the release dimensions usable as query filters for an app.

Use this to discover which tracks and version codes can appear in a query_vitals filter expression.

Report how current each vitals metric set's data is.

Call this before acting on a vitals number. Play data lags reality by hours to days, so a query covering "the last 7 days" can silently return five — and the absent days look like an improvement rather than a gap.

Get metadata for one vitals metric set, including its freshness.

Query an app vitals metric set timeline.

Covers every vital Play exposes: crash rate, ANR rate, slow start, slow rendering, excessive wake-ups, stuck background wakelocks, low-memory-killer rate and error counts. Call list_metric_sets for the available keys and get_vitals_freshness to check the data is current before drawing conclusions.

List statistical anomalies Play detected across the vitals metric sets.

Search grouped error issues — clusters of similar crashes or ANRs.

Search raw error reports — individual crashes and ANRs with stack traces.

Dry-run an edit: open one, validate it, then discard it.

Nothing is committed. Most useful as a permissions probe before a deploy — a failure here means the service account cannot publish, which is better learned before a release than during one.

Read which countries a track is distributed to.

Update app-level details: default language and store contact information.

Only the fields supplied are changed; the rest are read from the current details and written back unchanged, because the Play API replaces the whole resource on update.

Create a custom closed-testing track.

The four built-in tracks (internal, alpha, beta, production) always exist. This creates an additional named track, which is how closed testing groups beyond the built-ins are set up.

Update a track's release configuration.

Delete one locale's store listing.

Delete every localized store listing for an app.

Destructive: the listing text for all locales is removed in one commit and the API offers no undo. Two-step: preview, then confirm.

Register an APK hosted outside Play (enterprise distribution only).

Usable only by organisations enrolled in Play for Work private-channel distribution; a normal developer account receives a 403.

Point a version's OBB at one already uploaded against another version.

Large apps reuse the same expansion file across builds. This associates an existing OBB with a new version code instead of re-uploading it. Uses the API's patch (partial) semantics.

Set a version's OBB reference, replacing the whole resource.

Same effect as patch_expansion_file but with the API's update (full replace) semantics.

Acknowledge a subscription purchase.

Google automatically refunds and revokes any subscription purchase that is not acknowledged within three days, so this must run for every new subscription purchase.

Archive a subscription.

Play recommends archiving rather than deleting any subscription that has ever been purchased: deletion is rejected once purchases exist, and archiving preserves the record for existing subscribers.

Convert one source price into every Play region's price.

Returns Play's own recommended prices rather than a naive FX conversion — values are rounded to each region's local price conventions.

Retract a developer reply to a review.

The Play API has no delete-reply endpoint. The reply is retracted by replying again with empty text, which clears the visible reply; the result records the mechanism so this is not mistaken for erasure from history.

Verify the Play reports bucket is configured and readable. Run this first.

Installs, ratings, earnings and search terms come from a private Cloud Storage bucket rather than an API, and it needs separate setup: the bucket id in GOOGLE_PLAY_MCP_REPORTS_BUCKET, and the ACCOUNT-level Play Console permission "View app information and download bulk reports".

Returns: A diagnosis with the exact remedy when something is missing

List the bulk-report families this server can read.

Returns: Each family's key, bucket prefix, available dimensions and description. A family Google no longer publishes carries a discontinued note — those return no rows for recent months by design, not by failure.

List raw object names under a prefix in the reports bucket.

Diagnostic tool: use it when a report comes back empty to see what Play has actually published.

Daily and active-device installs, uninstalls and upgrades for one month.

Daily and total average rating for one month.

Daily crash and ANR counts for one month.

Distinct from query_vitals: this is a raw daily count from the bulk report, while the Reporting API gives user-weighted rates against Google's bad-behaviour thresholds. Use query_vitals to judge release health.

Store-listing acquisitions by traffic source or country.

Traffic sources are Play's own: Explore, Search, and Ads / referrals. For visitors and conversion rate use get_store_conversion_report.

Store-listing visitors, acquisitions and visitor-to-install conversion rate.

The underlying rows also break down by SEARCH TERM and UTM campaign — this is the only place either is available anywhere in Play's APIs. Use get_search_terms for the search-term view specifically.

What users searched to find the app, with acquisitions per term.

Pure ASO data available from no Play API — it exists only in the store performance CSV. Terms are ranked by acquisitions.

New, cancelled and active subscriptions by country for one month.

Transaction-level earnings for one month, in merchant currency.

Totals are reported PER CURRENCY and never summed across currencies — adding 1000 JPY to 10 EUR would be a wrong answer that looks like a right one, and this server has no exchange rates.

Earnings for a month are published around the 5th of the following month. Before that the report does not exist, and the freshness block says so rather than reporting zero revenue.

Search the public Play Store as a user in a given country would see it.

Store ranking is country- and language-specific, so those arguments change the answer rather than decorate it. Use this for competitor research and to see where an app ranks for a term.

Read any app's public store listing — including a competitor's.

Browse a store chart: top free, top paid or top grossing.

Play's own autocomplete suggestions for a keyword.

These are the terms Play believes users actually type, which is the closest thing to keyword volume the public store exposes. Pair with get_search_terms (bulk reports) to see which of them actually converted for your app.

Read public reviews, going back further than the Reviews API can.

The authenticated get_reviews tool returns roughly ONE WEEK — that is the API's limit, not this server's. Scraping is the only way to read older reviews, and it works for competitors' apps too.

The collection, category, sort and age values the store tools accept.

Returns: Valid values per argument

Check listing text against Play POLICY limits, not just what the API accepts.

The distinction matters: the Android Publisher API accepts a 50-character title and Play then rejects the app at review, because policy caps titles at 30. A title between 31 and 50 characters is reported as a warning — it will upload successfully and fail review.

Use validate_listing_text for the API-level check before an upload; use this before deciding on the text.

Check a Data Safety CSV export before declaring it.

Play has no API to read the current Data Safety declaration, and set_data_safety replaces it wholesale, so this is the only point at which the file can be inspected. Play's own rejection arrives after the upload and does not name the row.

Structural faults are errors: wrong headers, a row that is not five fields, a Response value that is not exactly TRUE/FALSE/blank (a lowercase "true" is the signature of a spreadsheet re-save), a repeated response, or a single-choice question with two answers.

Everything conditional is a warning. Google adds and renames question IDs without publishing them, and most of a real export is conditional on answers elsewhere in it, so an unrecognised ID or an unanswered group means "look at this", never "stop".

Play's requirements for every store-listing image type.

Returns: Per type: accepted formats, whether an alpha channel is required or forbidden, exact or bounded dimensions, aspect limit and size cap

Check one image against Play's rules before uploading it.

Reads the file's own header rather than trusting its extension — a .png that is really a JPEG is something export pipelines produce, and Play reads the bytes too.

Returns every problem at once rather than the first, so a fix round-trip handles all of them.

Check a whole screenshot set — every file, plus Play's count rules.

Play requires at least TWO screenshots per type per locale and caps at eight. A set of one is the common failure and it is invisible file by file, because each individual image is perfectly valid.

Open a draft edit and return its ID.

Nothing reaches users until commit_edit. Stage changes against the returned edit ID, inspect with describe_edit, then commit once.

Edits expire after about seven days. An abandoned one is harmless but worth discarding with delete_edit.

Read back everything currently staged in an open edit.

Use before committing. Sections that cannot be read are listed under unreadable rather than failing — an edit with no listings staged returns 404 for listings, which is information, not an error.

Dry-run an open edit without committing or discarding it.

Unlike validate_edit, which opens and throws away its own edit, this checks one you are building.

Commit an edit, publishing everything staged in it.

Two-step. The preview is read back from Play — it lists the track releases, listing locales and binaries actually staged — because the content came from earlier calls rather than this one's arguments.

Discard an open edit. Nothing staged in it takes effect.

Not gated: discarding a draft is the safe direction, and an agent that has to ask permission to clean up leaves edits open instead.

Call any Android Publisher v3 method directly, by dotted path.

An escape hatch for endpoints this server has not wrapped and for ones Google ships after this release. Prefer the dedicated tools: they validate input, normalise output and carry the safety rules. Use this when there is no dedicated tool.

Read methods run immediately. Anything that mutates is a two-step confirmed write, decided from the HTTP verb the API itself uses.

Which locales have a store listing, and which targets are still missing.

Copy a store listing's TEXT from one locale to another.

Copies title, descriptions and video. Images are not cloned — that means downloading and re-uploading every asset, a different operation with different failure modes.

A locale that already has a listing is left alone unless overwrite is set, so this cannot silently replace translated copy with the source language.