Google Play Games Services API
Browse all Google APIs41
AI ReadinessFoundational (D-)41/100
Official vendor OpenAPI document · agent-readyMediaContent Deliveryoauth239 EndpointsREST
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.
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.
Install Jentic One Beta
Connect the Google Play Games Services 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 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgames" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgames" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 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
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
Use Cases
Patterns agents use Google Play Games Services 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.
Key Endpoints
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
GET
/games/v1/achievements
List achievements defined for the game
POST
/games/v1/achievements/{achievementId}/unlock
Unlock an achievement for the player
POST
/games/v1/achievements/{achievementId}/increment
Increment a stepwise achievement
POST
/games/v1/achievements/{achievementId}/reveal
Reveal a hidden achievement
POST
/games/v1/achievements/updateMultiple
Apply a batch of achievement updates
POST
/games/v1/applications/played
Mark the application as played for the user
POST
/games/v1/accesstokens/generatePlayGroupingApiToken
Generate a Play Grouping token
GET
/games/v1/achievements
List achievements defined for the game
POST
/games/v1/achievements/{achievementId}/unlock
Unlock an achievement for the player
POST
/games/v1/achievements/{achievementId}/increment
Increment a stepwise achievement
POST
/games/v1/achievements/{achievementId}/reveal
Reveal a hidden achievement
POST
/games/v1/achievements/updateMultiple
Apply a batch of achievement updates
POST
/games/v1/applications/played
Mark the application as played for the user
POST
/games/v1/accesstokens/generatePlayGroupingApiToken
Generate a Play Grouping token
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
Google Play Games Services API
- Foundational (D-)41/100
46
Foundational Compliance56
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability63
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
46
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
85%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
77%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
67%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Google Play Games Services API by hand means setting up Google OAuth 2.0 with the games scope, refreshing short-lived bearer tokens, and mapping each achievement and application operation from Google's spec. Through Jentic you install once, import the Google Play Games Services API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This runtime API mixes collection endpoints and identifiers, so scope the agent to the operations it needs, such as unlocking or incrementing an achievement. You choose that operation set, so bulk calls like updateMultiple are not included unless you add them.
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 'unlock a Play Games achievement' or 'increment achievement progress', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Google Play Games Services 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.
Can I limit what my agent is allowed to do with the Google Play Games Services API?
Yes. Because you run Jentic One yourself, your own rules decide which Google Play Games operations and credentials the agent may use. This runtime API mixes collection endpoints and identifiers, so you can scope the agent to only the operations it needs, such as unlocking or incrementing an achievement, while leaving out others. Broad calls like the batch achievements updateMultiple endpoint stay unavailable unless you explicitly add them to the agent's allowed set.
GET STARTED