Terminal
Terminal/Skill
Guide to managing Google Play product and subscription catalogs through the Android Publisher API, including bulk updates and regional pricing.
By RevenueCat
Works with
npx skills add revenuecat/play-billing-skills --skill catalog-managementManage Google Play product catalogs at scale through the Android Publisher API. This skill helps you choose between Play Console and API based workflows, wire up the right endpoints for one time products and subscriptions, and keep regional pricing in sync with your source of truth.
Confirm the basics before writing catalog code.
inappproducts, monetization.onetimeproducts, and monetization.subscriptions calls return 403. Verify in Play Console under Users and permissions, then grant app level access to every package you intend to manage.inappproducts. Products created through the new service live under monetization.onetimeproducts. Once migrated, the legacy surface stops serving that product.monetization.onetimeproducts.list and monetization.subscriptions.list. Record product IDs, base plan IDs, offer IDs, and activation state so you know what you are mutating.Choose the management model that matches your scale.
| Catalog size | Recommended surface | Notes |
|---|---|---|
| Under 100 products, rare changes | Play Console UI | No automation overhead. Manual review before every change. |
| 100 to 10,000 products | batchUpdate with allowMissing=true, latency tolerant | Chunks of 100 clear the full catalog in minutes. |
| Over 10,000 products | batchUpdate with pacing, latency tolerant | Add inter batch delay, schedule off peak, run dry runs locally. |
Pick the right update mechanism per operation:
patch with an updateMask for targeted field changes on a single product.batchUpdate for bulk creates and updates, including nested base plans and offers on subscriptions.inappproducts.update only when you want to replace an entire legacy product resource and you send every field.Plan the activation state explicitly. Base plans created through the API start in DRAFT. Users cannot purchase until you call monetization.subscriptions.basePlans.activate. Write the activation step into your runbook so you do not ship dark products.
Plan reconciliation before you plan writes. Define a policy for each diff class:
allowMissing=true.updateMask your system manages.Add a safety rail: if a reconciliation run proposes changes to more than a threshold percentage of the catalog, fail closed and require manual review.
| Capability | One time product | Subscription |
|---|---|---|
| Create | monetization.onetimeproducts.create | monetization.subscriptions.create |
| Targeted update | monetization.onetimeproducts.patch | monetization.subscriptions.patch |
| Bulk create/update | monetization.onetimeproducts.batchUpdate | monetization.subscriptions.batchUpdate |
| List | monetization.onetimeproducts.list | monetization.subscriptions.list |
| Delete | monetization.onetimeproducts.delete / batchDelete | monetization.subscriptions.delete (only if never activated) |
| Activate | n/a | monetization.subscriptions.basePlans.activate |
| Deactivate | n/a | monetization.subscriptions.basePlans.deactivate |
| Price migration | n/a | monetization.subscriptions.basePlans.migratePrices |
val request = BatchUpdateOneTimeProductsRequest().apply {
requests = chunk.map { product ->
UpdateOneTimeProductRequest().apply {
oneTimeProduct = product
allowMissing = true
latencyTolerance =
"PRODUCT_UPDATE_LATENCY_TOLERANCE_LATENCY_TOLERANT"
}
}
}
androidPublisher.monetization()
.onetimeproducts()
.batchUpdate(packageName, request)
.execute()
Send chunks of 100. Each batch counts as one query against the per minute and hourly modification tiers.
val subscription = Subscription().apply {
listings = listOf(
SubscriptionListing().apply {
languageCode = "en-US"
title = "Premium Plan"
description = "Access all premium features"
}
)
}
androidPublisher.monetization().subscriptions()
.patch(packageName, productId, subscription)
.setUpdateMask("listings")
.execute()
When patching regional pricing fields, include regionsVersion in the body so the call uses the current region configuration.
androidPublisher.monetization().subscriptions()
.basePlans()
.activate(
packageName, productId, basePlanId,
ActivateBasePlanRequest()
)
.execute()
A subscription is not purchasable until at least one base plan is activated.
For one time products, prefer removing them from your storefront while leaving the catalog entry intact, so restore flows still resolve product IDs. Only call monetization.onetimeproducts.delete when you are sure no restore path references the product.
For subscriptions, deactivate all base plans to stop new signups while existing subscribers continue renewing:
androidPublisher.monetization().subscriptions()
.basePlans()
.deactivate(
packageName, productId, basePlanId,
DeactivateBasePlanRequest()
)
.execute()
Delete the subscription itself only when no base plan has ever been activated. After activation, deactivation is the terminal state.
Regional price updates are high volume operations, so route them through batch methods with latency tolerant mode. Build the full region map locally, then submit batchUpdate calls of up to 100 products per request. For subscriptions that already have subscribers on older prices, follow the bulk update with monetization.subscriptions.basePlans.migratePrices to move existing subscribers onto the new price version.
On HTTP 429 with reason: rateLimitExceeded, back off exponentially and resume. Keep batches at latency tolerant mode whenever visibility within 24 hours is acceptable, which keeps the hourly latency sensitive tier free for real time fixes like pricing corrections.