Gplay Iap Setup

Handles the configuration of in-app purchases and subscriptions for Google Play, covering both the legacy API and the newer monetization endpoints. The big gotcha is that product IDs are permanent once created, even after deletion, so you can't reuse a burned ID. The skill documents the two competing APIs (the legacy inappproducts vs the new onetimeproducts) and makes it clear you should use the new one unless you're managing old products. It walks through the full lifecycle: creating products with regional pricing, activating purchase options (new products start in DRAFT), and setting up subscription base plans and offers. Useful if you're wiring up monetization and need to remember which price format or regions-version flag applies to which API.

skills.sh installs: 421
GitHub stars: 52
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tamtom/gplay-cli-skills --skill gplay-iap-setup --agent claude-code

Installs into .claude/skills of the current project.

Files

In-App Purchase Setup for Google Play

Use this skill when you need to set up monetization for your Android app.

Two APIs: Legacy vs New Monetization

Google Play has two APIs for one-time products:

	Legacy (`gplay iap`)	New Monetization (`gplay onetimeproducts`)
API	`inappproducts`	`monetization.onetimeproducts`
Price format	`priceMicros`/`currency`	`units`/`nanos`/`currencyCode`
Structure	Flat `prices` map	`purchaseOptions` with `regionalPricingAndAvailabilityConfigs`
States	`active`/`inactive`	`DRAFT` → `ACTIVE` (requires explicit activation)
Regional pricing	`--auto-convert-prices` flag	`--regions-version` required

Prefer the new monetization API (gplay onetimeproducts) for new products. It supports purchase options, better regional pricing control, and is the actively developed API.

Use the legacy API (gplay iap) only for managing existing legacy products.

Never mix the two APIs for the same product. A product created via gplay iap create cannot be managed via gplay onetimeproducts and vice versa.