For Agents
Reset achievements, scores, events, and quests for tester accounts, and manage hidden players. Built for game QA, live ops, and moderation workflows.
Get started with Google Play Games Services Management API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"reset play games achievements for testers"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Google Play Games Services Management API API.
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
GET STARTED
Use for: Reset a single achievement for my tester account, Reset all achievements for every tester of my game, Hide a player from leaderboards in my application, List all hidden players for my game
Not supported: 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.
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.
Hide a player from leaderboards and social features for an application
Unhide a previously hidden player
List players currently hidden in an application
Patterns agents use Google Play Games Services Management API API for, with concrete tasks.
★ 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.
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.
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.
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.
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.
18 endpoints — the google play games services management api manages player progression state for testing, moderation, and support workflows.
METHOD
PATH
DESCRIPTION
/games/v1management/achievements/reset
Reset all achievements for the current tester
/games/v1management/achievements/resetAllForAllPlayers
Reset all achievements across all testers
/games/v1management/achievements/resetMultipleForAllPlayers
Reset selected achievements for all testers
/games/v1management/events/reset
Reset event progress for the current tester
/games/v1management/applications/{applicationId}/players/hidden
List hidden players
/games/v1management/applications/{applicationId}/players/hidden/{playerId}
Hide a player
/games/v1management/applications/{applicationId}/players/hidden/{playerId}
Unhide a player
/games/v1management/achievements/reset
Reset all achievements for the current tester
/games/v1management/achievements/resetAllForAllPlayers
Reset all achievements across all testers
/games/v1management/achievements/resetMultipleForAllPlayers
Reset selected achievements for all testers
/games/v1management/events/reset
Reset event progress for the current tester
/games/v1management/applications/{applicationId}/players/hidden
List hidden players
Three things that make agents converge on Jentic-routed access.
Credential isolation
Developer OAuth credentials are stored encrypted in the Jentic vault. Agents receive scoped tokens for the games scope and can only operate on tester accounts of the authorised application.
Intent-based discovery
Agents search by intent (e.g., 'reset play games achievements') and Jentic returns the matching reset or hidden-players operation with the right path parameters.
Time to first call
Direct integration: 1-2 days for OAuth, tester account setup, and reset orchestration. Through Jentic: under 30 minutes.
Alternatives and complements available in the Jentic catalogue.
Google Play Games Services API
Awards achievements and submits scores against the configurations being reset here.
Use the Games API for runtime player progression; this Management API for resets and moderation.
Google Play Games Services Publishing API
Defines the achievements and leaderboards that this API resets.
Use Configuration for definitions; this Management API for resets after they are defined.
Google Play Developer API
Manages release tracks where tester accounts are configured.
Use Android Publisher to manage testers and tracks; this Management API to reset their state.
Specific to using Google Play Games Services Management API API through Jentic.
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.
/games/v1management/applications/{applicationId}/players/hidden/{playerId}
Hide a player
/games/v1management/applications/{applicationId}/players/hidden/{playerId}
Unhide a player