Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(8 of 274)

Books API

The Google Books API gives applications structured access to the Google Books repository, covering volume metadata, full-text search, bookshelves, reviews, and personal library management. It supports public catalog discovery as well as authenticated user-library operations such as bookshelf manipulation, reading position tracking, and offline metadata sync. The API is widely used to build reading apps, library tools, citation utilities, and book recommendation features.

51 endpoints

Google Play Games Services API

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.

39 endpoints

Google Play Games Services Management API

The Google Play Games Services Management API manages player progression state for testing, moderation, and support workflows. It resets achievements, scores, events, and quests for individual test accounts or for all tester accounts at once, and lets developers hide or unhide players within an application. Use it from QA pipelines and live ops tools, never against real player data.

18 endpoints

Google Play Games Services Publishing API

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.

10 endpoints

Reader Revenue Subscription Linking API

The Reader Revenue Subscription Linking API lets news publishers tie a Google reader identity to a publisher subscription so that signed-in Google users see their entitlements honored across Google surfaces. Publishers exchange reader IDs and subscription metadata with Google to mark a reader as entitled, update existing entitlements, or remove the link when a subscription ends. The API is the connective tissue between a publisher's subscription system of record and Google's reader-facing surfaces.

3 endpoints

Transcoder API

Transcoder API converts source video files into streaming-ready and downloadable formats including HLS, DASH, MP4, and WebM, applying multiple bitrates, codecs, and resolutions in a single job. It supports adaptive bitrate ladders, audio track muxing, sprite-sheet generation, ad insertion markers, and image overlays. Job templates encapsulate frequently used encoding settings, so production workflows submit jobs by template name plus input/output Cloud Storage URIs rather than re-specifying ladder parameters per file.

6 endpoints

Web Fonts Developer API

The Google Web Fonts Developer API exposes the catalogue of font families served by Google Fonts so that applications can programmatically discover available typefaces, variants, subsets, and category metadata. The API is read-only and returns the same font index that powers the Google Fonts directory, including version, last-modified date, files per variant, and supported scripts. It is most useful for building font pickers, design tools, and CMS integrations that need an up-to-date list of free, open-source web fonts.

1 endpoints

YouTube Data API v3

Access and manage YouTube video content, channels, playlists, comments, live streams, and captions programmatically. Supports video search across YouTube's catalog of over 800 million videos, channel analytics retrieval, playlist curation, comment moderation, and live broadcast management. Enables both read-only access to public data via API keys and full account management via OAuth 2.0 scopes including upload, rating, and subscription operations.

82 endpoints

Connect Your Agent

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.