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.
Get started with Google Play Games Services Publishing 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:
"create a play games achievement"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Google Play Games Services Publishing API 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
GET STARTED
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.
List all achievements or leaderboards configured for an application
Retrieve a single achievement or leaderboard by id
Patterns agents use Google Play Games Services Publishing API 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.
10 endpoints — the google play games services publishing api lets developers configure their games' play games services resources programmatically.
METHOD
PATH
DESCRIPTION
/games/v1configuration/applications/{applicationId}/achievements
List achievement configurations
/games/v1configuration/applications/{applicationId}/achievements
Create an achievement
/games/v1configuration/achievements/{achievementId}
Get a single achievement configuration
/games/v1configuration/achievements/{achievementId}
Update an achievement configuration
/games/v1configuration/achievements/{achievementId}
Delete an achievement
/games/v1configuration/applications/{applicationId}/leaderboards
List leaderboard configurations
/games/v1configuration/applications/{applicationId}/leaderboards
Create a leaderboard
/games/v1configuration/applications/{applicationId}/achievements
List achievement configurations
/games/v1configuration/applications/{applicationId}/achievements
Create an achievement
/games/v1configuration/achievements/{achievementId}
Get a single achievement configuration
/games/v1configuration/achievements/{achievementId}
Update an achievement configuration
/games/v1configuration/achievements/{achievementId}
Delete an achievement
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 that can configure Play Games resources only for the authorised developer account.
Intent-based discovery
Agents search by intent (e.g., 'create a play games achievement') and Jentic returns the matching configuration operation with its full request schema.
Time to first call
Direct integration: 1-2 days for OAuth, achievement schema, and reconciliation logic. Through Jentic: under 30 minutes.
Alternatives and complements available in the Jentic catalogue.
Google Play Games Services API
Awards achievements and posts scores at runtime against configurations made here.
Use the Games API for runtime player operations; this Publishing API for definitions.
Google Play Games Services Management API
Resets achievements and scores during testing.
Use Management to clear state in test accounts after configuring with this API.
Google Play Developer API
Manages app listings and releases on the Play Store.
Use Android Publisher for store metadata and releases; this API for in-game configurations.
Specific to using Google Play Games Services Publishing API 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.
/games/v1configuration/applications/{applicationId}/leaderboards
List leaderboard configurations
/games/v1configuration/applications/{applicationId}/leaderboards
Create a leaderboard