canonical: https://jentic.com/apis/googleapis.com/games-management

# Google Play Games Services Management API

The Google Play Games Services Management API manages player progression state for testing, moderation, and support workflows. It resets achievements, scores, events, and quests for individual test accounts or for all tester accounts at once, and lets developers hide or unhide players within an application. Use it from QA pipelines and live ops tools, never against real player data.

## For AI agents

Reset achievements, scores, events, and quests for tester accounts, and manage hidden players. Built for game QA, live ops, and moderation workflows.

## Scope

Does not configure achievements or leaderboards, award progression, or modify real player data - use the Configuration API for setup and the Games API for runtime; this API only resets tester state and manages hidden players.

## Capabilities

- Reset a single achievement for the current tester account
- Reset all achievements for every tester of an application
- Reset multiple specific achievements for all testers in one call
- Reset event progress and quest state for testers
- Hide a player from leaderboards and social features for an application
- Unhide a previously hidden player
- List players currently hidden in an application

## Use cases

### QA Account Reset Between Test Runs

Game QA teams need a clean baseline of achievements and scores before each regression pass. The Management API resets a single achievement, all achievements, or selected achievements for the current tester account or all testers, allowing automated test suites to start from a known state. This removes the need for engineers to wipe state manually in the Play Console.

Example prompt: Call POST /games/v1management/achievements/reset before each test run to clear all achievements for the current tester account.

### Moderate Disruptive Players

Live games occasionally need to remove abusive players from leaderboards and social features. The hidden players endpoints let support staff hide a player by id within an application, removing them from leaderboard windows and friend listings, and unhide them later if appropriate. The action is reversible and scoped to the application.

Example prompt: Call POST /games/v1management/applications/{applicationId}/players/hidden/{playerId} to hide an abusive player and confirm with GET on the hidden players list.

### Pre-Release Reset Across All Testers

Before a release candidate ships to closed testers, studios reset all progression so testers experience the new build from zero. The resetAllForAllPlayers endpoints reset achievements, events, and quests for every tester account at once, enabling clean regression and balance verification.

Example prompt: Call POST /games/v1management/achievements/resetAllForAllPlayers, /games/v1management/events/resetAllForAllPlayers, and the equivalent quests endpoint before promoting the build.

### Agent-Run Test Hygiene

An AI agent embedded in a CI workflow can reset achievement and event state on tester accounts between runs through Jentic. The agent searches for the reset operation, loads its schema, and executes it as part of the pipeline, freeing engineers from writing custom OAuth glue.

Example prompt: Use Jentic to search 'reset play games achievements', load the achievements/reset schema, and execute it as part of the pipeline before integration tests run.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /games/v1management/achievements/reset | Reset all achievements for the current tester |
| POST | /games/v1management/achievements/resetAllForAllPlayers | Reset all achievements across all testers |
| POST | /games/v1management/achievements/resetMultipleForAllPlayers | Reset selected achievements for all testers |
| POST | /games/v1management/events/reset | Reset event progress for the current tester |
| GET | /games/v1management/applications/{applicationId}/players/hidden | List hidden players |
| POST | /games/v1management/applications/{applicationId}/players/hidden/{playerId} | Hide a player |
| DELETE | /games/v1management/applications/{applicationId}/players/hidden/{playerId} | Unhide a player |

## Key resources

- **achievements** — Reset single, all, or multiple achievements for testers.
- **events** — Reset event progress for testers.
- **quests** — Reset quest progress for testers.
- **players (hidden)** — Hide and unhide players from an application's leaderboards and social features.

## Why Jentic

- **Setup:** Wiring the Google Play Games Services Management API by hand means setting up Google OAuth 2.0 with the games scope for the authorised application and coding the reset and hidden-player calls from Google's spec. Through Jentic you install once, import the Google Play Games Services Management API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** This API puts the application and player in the URL path (/games/v1management/applications/{applicationId}/players/hidden/{playerId}), so a rule can pin your agent to one application and its hidden players and nothing else. You choose the operations it may call, so wide resets like resetAllForAllPlayers are not included unless you add them.
- **Credential handling:** Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'reset Play Games achievements for a tester' or 'list hidden players', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Google Play Games Services API** — Awards achievements and submits scores against the configurations being reset here.
- **Google Play Games Services Publishing API** — Defines the achievements and leaderboards that this API resets.
- **Google Play Developer API** — Manages release tracks where tester accounts are configured.

## FAQ

### What authentication does the Play Games Services Management API use?

It uses Google OAuth 2.0 with the games scope, but most endpoints only function for tester accounts associated with the developer's application. Through Jentic, OAuth credentials live encrypted in the vault.

### Can I reset a real player's achievements with this API?

No. Reset endpoints only work for tester accounts configured in the Play Console for the application. Calls against real player accounts return errors and have no effect.

### What are the rate limits for the Play Games Services Management API?

Google enforces standard per-project quotas, typically a few hundred requests per minute. Reset operations across all testers should be paced and retried on HTTP 429.

### How do I hide a player from a leaderboard through Jentic?

Search Jentic for 'hide a play games player', load the schema for POST /games/v1management/applications/{applicationId}/players/hidden/{playerId}, and execute it for the target playerId.

### Is the Play Games Services Management API free?

Yes, the API itself has no cost. A Google Play developer account and a configured application are required to use it.

### Can I configure achievements with this API?

No. Achievement and leaderboard definitions are managed via the Play Games Services Publishing API. This API only manages player state and moderation.

### Can I limit what my agent is allowed to do with the Google Play Games Services Management API?

Yes. Jentic One is self-hosted, so you run it and your own rules decide which operations and credentials your agent may use. Because this API puts the application and player in the URL path, such as /games/v1management/applications/{applicationId}/players/hidden/{playerId}, you can pin the agent to a single application and only its hidden-player actions like hide, unhide, and list. You also choose the exact operations it may call, so wide resets such as achievements resetAllForAllPlayers are excluded unless you deliberately add them, and your OAuth credential is injected only at execution time and never reaches the agent's prompt.