Google Play Games Services Publishing API
Browse all Google APIs39
AI ReadinessNon-Ready (F)39/100
Official vendor OpenAPI document · agent-readyMediaContent Deliveryoauth210 EndpointsREST
For Agents
Define and update Play Games achievements and leaderboards programmatically, including titles, descriptions, and ordering. Built for game tooling that needs configuration-as-code.
Use for: Create a new achievement for my game, Update the description of an existing achievement, List all leaderboards configured for my application, Delete an achievement that is no longer used
Not supported: Does not award achievements, post scores, or reset player state - use the Games API for runtime and the Games Management API for resets; this API is for configuration only.
The Google Play Games Services Publishing API lets developers configure their games' Play Games Services resources programmatically. It manages the definition of achievements and leaderboards under an application, including localised metadata, sort order, and image references. Use it from build pipelines to keep game configuration in source control and apply changes without clicking through the Play Console.
Install Jentic One Beta
Connect the Google Play Games Services Publishing 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 Publishing 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-configuration" | 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-configuration" | 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 Publishing API.
Create new achievements under a game application
Update achievement metadata such as name, description, and image
Delete achievements that are no longer needed
Create and update leaderboards with sort order and time scopes
List all achievements or leaderboards configured for an application
Retrieve a single achievement or leaderboard by id
Use Cases
Patterns agents use Google Play Games Services Publishing API for, with concrete tasks.
★ Configuration-as-Code for Game Releases
Game studios that ship frequent updates want their Play Games configuration in version control alongside game code. The Publishing API lets a CI pipeline reconcile a JSON or YAML manifest of achievements and leaderboards against the live application configuration, creating, updating, or deleting entries as needed. This removes manual Play Console clicks and keeps environments consistent.
Call POST /games/v1configuration/applications/{applicationId}/achievements for each new achievement defined in the release manifest.
Localise Achievement Strings
Games shipping in multiple languages need localised achievement titles and descriptions. The achievements update endpoint accepts localised string sets, so a translation pipeline can push new locales into Play Games without engineering involvement. The configuration is then served by the Play Games SDK in the player's language at runtime.
Call PUT /games/v1configuration/achievements/{achievementId} with an updated achievementName containing localised string entries for additional locales.
Audit Leaderboard Configuration
Live operations teams need to verify which leaderboards are configured against an application before a tournament. The list leaderboards endpoint returns every leaderboard with sort order, score format, and identifier, enabling automated checks that the right boards exist before enabling them in the client.
Call GET /games/v1configuration/applications/{applicationId}/leaderboards and verify the expected leaderboard ids and sort orders are present.
Agent-Generated Achievement Sets
An AI assistant for game designers can propose an achievement set for a new game mode and apply it to the Play Console via Jentic. The agent searches for the create achievement operation, loads its schema, and creates each achievement with name, description, and points. The designer reviews the live configuration in the Play Console before publishing.
Use Jentic to search 'create a play games achievement', load the schema for POST /games/v1configuration/applications/{applicationId}/achievements, and execute it for each generated achievement.
Key Endpoints
10 endpoints — the google play games services publishing api lets developers configure their games' play games services resources programmatically.
METHOD
PATH
DESCRIPTION
GET
/games/v1configuration/applications/{applicationId}/achievements
List achievement configurations
POST
/games/v1configuration/applications/{applicationId}/achievements
Create an achievement
GET
/games/v1configuration/achievements/{achievementId}
Get a single achievement configuration
PUT
/games/v1configuration/achievements/{achievementId}
Update an achievement configuration
DELETE
/games/v1configuration/achievements/{achievementId}
Delete an achievement
GET
/games/v1configuration/applications/{applicationId}/leaderboards
List leaderboard configurations
POST
/games/v1configuration/applications/{applicationId}/leaderboards
Create a leaderboard
GET
/games/v1configuration/applications/{applicationId}/achievements
List achievement configurations
POST
/games/v1configuration/applications/{applicationId}/achievements
Create an achievement
GET
/games/v1configuration/achievements/{achievementId}
Get a single achievement configuration
PUT
/games/v1configuration/achievements/{achievementId}
Update an achievement configuration
DELETE
/games/v1configuration/achievements/{achievementId}
Delete an achievement
GET
/games/v1configuration/applications/{applicationId}/leaderboards
List leaderboard configurations
POST
/games/v1configuration/applications/{applicationId}/leaderboards
Create a leaderboard
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 Publishing API
- Non-Ready (F)39/100
62
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
62
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B-Signals: 4
88%
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).
60%
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.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
69%
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).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
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 Publishing API by hand means setting up Google OAuth 2.0 for the authorised developer account and coding the achievement and leaderboard configuration calls from Google's spec. Through Jentic you install once, import the Google Play Games Services Publishing API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This configuration API puts the application in the URL path (/games/v1configuration/applications/{applicationId}/achievements, /games/v1configuration/applications/{applicationId}/leaderboards), so a rule can pin your agent to one application: it can list and create achievements and leaderboards there and nothing else. You choose the operations it may call, so achievement deletion is not included unless you add it.
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 'create a Play Games achievement' or 'add a leaderboard', 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 Publishing API through Jentic.
What authentication does the Play Games Services Publishing API use?
It uses Google OAuth 2.0 with the androidpublisher scope, scoped to the developer account that owns the application. Through Jentic, those credentials live encrypted in the vault and agents receive only scoped bearer tokens.
Can I create achievements with this API?
Yes. Use POST /games/v1configuration/applications/{applicationId}/achievements with the achievement name, description, points, and image references to create a new achievement under the application.
What are the rate limits for the Play Games Services Publishing API?
Google enforces standard per-project quotas, typically around 60 write requests per minute. Bulk reconciliation jobs should pace requests and retry on HTTP 429.
How do I provision a new leaderboard through Jentic?
Search Jentic for 'create a play games leaderboard', load the schema for POST /games/v1configuration/applications/{applicationId}/leaderboards, and execute it with the leaderboard name, sort order, and score format.
Is the Play Games Services Publishing API free?
Yes, the API itself is free. A Google Play developer account and a configured application are required to use it.
Can I award achievements with this API?
No. Awarding achievements to players is done via the Google Play Games Services API. This Publishing API only configures the achievement definitions.
Can I limit what my agent is allowed to do with the Google Play Games Services Publishing API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this configuration API puts the application in the URL path (/games/v1configuration/applications/{applicationId}/achievements and /leaderboards), so a rule can pin the agent to a single application. You can allow it to list and create achievements and leaderboards there and nothing else, and you choose the operations it may call, so achievement deletion stays excluded unless you add it. The Google OAuth credential is injected only at execution time and never reaches the agent's prompt or logs.
GET STARTED