Google Play Games Services API

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

✓ Official Vendor SpecMediaContent Deliveryoauth239 Endpoints

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.

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 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

GET STARTED

Start building with Google Play Games Services API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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.

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.

Google Play Games Services API

Connect the Google Play Games Services API to your agent

Capabilities

Start building with Google Play Games Services API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs