2.6k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill google-play- _meta.json630 B
- LICENSE.txt1.0 KB
- SKILL.md11.0 KB
Overview
This skill integrates the Google Play Developer API (Android Publisher) with managed OAuth so you can programmatically manage apps, in-app products, subscriptions, purchases, reviews, and edits. It proxies native Android Publisher endpoints through a gateway and injects OAuth tokens, letting you call Google Play endpoints with a single API key. Use it to automate publishing tasks, subscription lifecycle operations, and review replies.
How this skill works
Requests are sent to a gateway base URL that mirrors Android Publisher paths; the gateway forwards calls to androidpublisher.googleapis.com and injects your OAuth token. Authentication uses a single MATON_API_KEY in the Authorization header. For multiple Google accounts, create and select connections via the control endpoint and pass a Maton-Connection header to target a specific Google Play account.
When to use it
- Automate publishing workflows (create edits, upload changes, commit edits).
- Manage in-app products and subscription definitions programmatically.
- Verify, acknowledge, cancel, or refund purchases using purchase tokens.
- List and reply to user reviews from scripts or CI jobs.
- Integrate Google Play operations into backend services without handling OAuth flows directly.
Best practices
- Keep MATON_API_KEY secret and store it in environment variables or a secure vault.
- Create and reuse active connections for each Google Play account to avoid repeated OAuth flows.
- Use edits for transactional app updates: create an edit, make changes, then commit.
- Respect rate limits (10 requests/sec per account) and implement exponential backoff on 429 responses.
- Include Maton-Connection header when working with multiple connections to avoid accidental account changes.
Example use cases
- CI job that creates an edit, updates APK/AAB metadata, and commits the edit to release an app update.
- Backend service that validates purchase tokens and acknowledges one-time purchases automatically.
- Admin dashboard that lists subscriptions and updates pricing or base plans via the API.
- Automated customer support tool that lists reviews and posts replies to user feedback.
- Script to bulk-create or update in-app products and localized listings from CSV data.
FAQ
Set MATON_API_KEY as an environment variable and include Authorization: Bearer $MATON_API_KEY in every request.
How do I target a specific Google Play account when I have multiple connections?
Create a connection via the control endpoint and include Maton-Connection: <connection_id> header on gateway requests to specify which Google Play connection to use.