Google Play Games Services Management API

Name: Google Play Games Services Management API
Brand: Google Play Games Services Management API
Availability: InStock

Browse all Google APIs

✓ Official Vendor SpecMediaContent Deliveryoauth218 Endpoints

Install Jentic One Beta

Connect the Google Play Games Services Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Play Games Services Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google Play Games Services Management 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

GET STARTED

Start building with Google Play Games Services Management API

Explore with Jentic

View OpenAPI Document

For Agents

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

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.

Use Cases

Patterns agents use Google Play Games Services Management 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.

Key Endpoints

18 endpoints — the google play games services management api manages player progression state for testing, moderation, and support workflows.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Google Play Games Services Management 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.

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.

Google Play Games Services Management API

Connect the Google Play Games Services Management API to your agent

Capabilities

Start building with Google Play Games Services Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs