Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(2 of 274)

Google Wallet API

The Google Wallet API lets issuers create and manage saveable passes including event tickets, boarding passes, loyalty cards, gift cards, offers, and generic passes. Each pass is modeled as a Class (the template) and an Object (the per-user instance), with separate endpoints for creating, updating, expiring, and posting messages to passes. Issuers also smart-tap signing keys, manage Jose JWT formats for the Add to Google Wallet button, and can fan out updates to all holders of a class.

98 endpoints

Payments Reseller Subscription API

The Payments Reseller Subscription API lets approved Google partners manage subscriptions on behalf of end users for Google products (such as YouTube Premium) sold through reseller channels. It exposes operations to find eligible promotions, list available products, provision a subscription for a user, and run lifecycle actions including cancel, suspend, resume, extend, undo cancel, and entitle. Use it to integrate Google subscription billing into a partner's checkout flow, manage post-sale lifecycle events, and apply qualifying promotions. The spec exposes 13 endpoints.

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