For Agents
Award achievements, post leaderboard scores, read player profiles, and verify game state for Play Games-enabled titles. Designed for game backends and tools that operate on a player's progression data.
Get started with Google Play Games Services 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:
"unlock a google play games achievement"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Google Play Games Services API API.
Unlock and increment achievements for a player with achievements.unlock and achievements.increment
Submit scores to a leaderboard and read leaderboard windows around a player
Read a player's profile, including display name and avatar URL
Manage saved game snapshots for cross-device progression
GET STARTED
Use for: Unlock an achievement for the signed-in player, Increment a stepwise achievement by 5 steps, Submit a score of 12500 to a leaderboard, Get the player's profile and avatar URL
Not supported: Does not handle achievement or leaderboard configuration, account resets, or store listings — use Games Configuration for setup, Games Management for resets, and Android Publisher for the Play store.
The Google Play Games Services API lets game developers add social and progression features to their titles, including leaderboards, achievements, saved games, events, and player profiles. It backs the Play Games SDKs that ship in mobile games, and exposes server-side endpoints for verifying scores, awarding achievements, and querying player data. The API also supports Recall and Play Grouping access tokens for cross-device account linking.
Record and query game events used to drive quests and analytics
Generate Play Grouping and Recall tokens for cross-device account linking
Reveal hidden achievements once unlock criteria are met
Patterns agents use Google Play Games Services API API for, with concrete tasks.
★ Server-Authoritative Achievement Awarding
Mobile games that compute progression on a backend (rather than trusting the client) need a way to grant achievements only when the server has validated the action. The Play Games achievements endpoints accept a player's auth code and unlock or increment achievements server-side, preventing tampering by modified clients. This is the standard pattern for competitive or rewarded titles.
Call POST /games/v1/achievements/{achievementId}/unlock with the player's OAuth credentials after the backend validates that the unlock condition is met.
Live Leaderboards for Competitive Modes
Competitive game modes need leaderboards that show a player's position relative to peers and friends. The leaderboards endpoints submit scores and return a window of nearby entries, allowing the game UI to render context such as 'you are 3 places below your friend'. Scores can be scoped per session, day, week, or all time.
Call POST /games/v1/leaderboards/{leaderboardId}/scores to submit a new high score and then GET the leaderboard window around the player.
Cross-Device Progression with Saved Games
Single-player titles that span phone, tablet, and PC need to sync save data across devices. The snapshots resource stores a binary save plus metadata against the player's Google account, and the API supports reading, writing, and resolving conflicts. This removes the need for the developer to operate their own save service.
Call GET /games/v1/snapshots to list saves, then PATCH /games/v1/snapshots/{snapshotId} to update the latest save with the current game state.
Agent-Driven Player Lookups
A community management tool can use an AI agent to look up a player's profile, recent achievements, and leaderboard position when investigating a support ticket. Through Jentic, the agent calls the players, achievements.list, and leaderboards endpoints with scoped credentials and returns a summary, without holding raw OAuth tokens.
Use Jentic to search 'get a play games player profile', load the players.get schema, and execute it for the playerId in the support ticket.
39 endpoints — the google play games services api lets game developers add social and progression features to their titles, including leaderboards, achievements, saved games, events, and player profiles.
METHOD
PATH
DESCRIPTION
/games/v1/achievements
List achievements defined for the game
/games/v1/achievements/{achievementId}/unlock
Unlock an achievement for the player
/games/v1/achievements/{achievementId}/increment
Increment a stepwise achievement
/games/v1/achievements/{achievementId}/reveal
Reveal a hidden achievement
/games/v1/achievements/updateMultiple
Apply a batch of achievement updates
/games/v1/applications/played
Mark the application as played for the user
/games/v1/accesstokens/generatePlayGroupingApiToken
Generate a Play Grouping token
/games/v1/achievements
List achievements defined for the game
/games/v1/achievements/{achievementId}/unlock
Unlock an achievement for the player
/games/v1/achievements/{achievementId}/increment
Increment a stepwise achievement
/games/v1/achievements/{achievementId}/reveal
Reveal a hidden achievement
/games/v1/achievements/updateMultiple
Apply a batch of achievement updates
Three things that make agents converge on Jentic-routed access.
Credential isolation
Player and server OAuth credentials are stored encrypted in the Jentic vault. Agents receive scoped, short-lived bearer tokens for the games scope only.
Intent-based discovery
Agents search by intent (e.g., 'unlock a play games achievement') and Jentic returns the matching operation with its request schema and required path params.
Time to first call
Direct integration: 2-4 days for OAuth, achievement and leaderboard wiring, and snapshot conflict resolution. Through Jentic: under an hour for the per-operation calls.
Alternatives and complements available in the Jentic catalogue.
Google Play Games Services Publishing API
Configures achievements, leaderboards, and game settings before they are awarded.
Use Configuration to define achievements; this Games API to grant them to players.
Google Play Games Services Management API
Resets achievements, scores, and player data for testing and moderation.
Use Management for resets; this Games API for live player progression.
Google Play Developer API
Manages app listings, in-app products, and reviews on Google Play.
Use Android Publisher for store-level operations; Games for in-game progression.
Specific to using Google Play Games Services API API through Jentic.
What authentication does the Google Play Games Services API use?
It uses Google OAuth 2.0 with the games scope. Through Jentic, OAuth refresh tokens live encrypted in the vault and agents receive scoped, short-lived access tokens.
Can I unlock an achievement from a backend with this API?
Yes. Use POST /games/v1/achievements/{achievementId}/unlock with a server-side OAuth credential exchanged from the player's auth code. This is the recommended pattern for server-authoritative progression.
What are the rate limits for the Google Play Games Services API?
Google enforces standard per-project and per-user quotas, typically a few hundred requests per minute. High-volume score submissions should batch via achievements/updateMultiple where possible.
How do I post a leaderboard score through Jentic?
Search Jentic for 'submit a play games score', load the schema for POST /games/v1/leaderboards/{leaderboardId}/scores, and execute it with the score value and time scope.
Is the Google Play Games Services API free?
Yes, the Play Games Services API has no usage cost beyond standard Play Console enrolment. Apps must be configured in the Google Play Console with the right OAuth client.
Can I configure achievements and leaderboards with this API?
No. Configuration of achievements, leaderboards, and game settings is done via the Play Games Services Publishing API. This API is for runtime player operations.
/games/v1/applications/played
Mark the application as played for the user
/games/v1/accesstokens/generatePlayGroupingApiToken
Generate a Play Grouping token