Google Wallet API

Name: Google Wallet API
Brand: Google Wallet API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controloauth298 EndpointsREST

For Agents

Programmatically walletobjects.eventticketclass.insert, walletobjects.eventticketclass.list. Covers 98 operations with oauth2 authentication.

Install Jentic One Beta

Connect the Google Wallet API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Wallet 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwalletobjects.googleapis.com%2Fwalletobjects-googleapis" | sh

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%2Fwalletobjects.googleapis.com%2Fwalletobjects-googleapis" | 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 Wallet API.

walletobjects.eventticketclass.insert

walletobjects.eventticketclass.list

walletobjects.eventticketclass.get

walletobjects.eventticketclass.update

GET STARTED

Start building with Google Wallet API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Google Wallet API for, with concrete tasks.

★ Developer Tools Operations

Use the Google Wallet API to perform developer tools operations programmatically. The API provides 98 endpoints covering core functionality including walletobjects.eventticketclass.insert, walletobjects.eventticketclass.list, walletobjects.eventticketclass.get.

Call POST /walletobjects/v1/eventTicketClass to walletobjects.eventticketclass.insert

Automated walletobjects Management

Automate walletobjects operations by combining multiple Google Wallet API endpoints. Agents can walletobjects.eventticketclass.list and then walletobjects.eventticketclass.get in a single workflow.

Call GET /walletobjects/v1/eventTicketClass to walletobjects.eventticketclass.list, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Google Wallet API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Search Jentic for 'walletobjects.eventticketclass.insert', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

98 endpoints — api for issuers to save and manage google wallet objects.

METHOD

PATH

DESCRIPTION

POST

/walletobjects/v1/eventTicketClass

walletobjects.eventticketclass.insert

GET

/walletobjects/v1/eventTicketClass

walletobjects.eventticketclass.list

GET

/walletobjects/v1/eventTicketClass/{resourceId}

walletobjects.eventticketclass.get

PUT

/walletobjects/v1/eventTicketClass/{resourceId}

walletobjects.eventticketclass.update

PATCH

/walletobjects/v1/eventTicketClass/{resourceId}

walletobjects.eventticketclass.patch

POST

/walletobjects/v1/eventTicketClass/{resourceId}/addMessage

walletobjects.eventticketclass.addmessage

POST

/walletobjects/v1/eventTicketObject

walletobjects.eventticketobject.insert

GET

/walletobjects/v1/eventTicketObject

walletobjects.eventticketobject.list

POST

/walletobjects/v1/eventTicketClass

walletobjects.eventticketclass.insert

GET

/walletobjects/v1/eventTicketClass

walletobjects.eventticketclass.list

GET

/walletobjects/v1/eventTicketClass/{resourceId}

walletobjects.eventticketclass.get

PUT

/walletobjects/v1/eventTicketClass/{resourceId}

walletobjects.eventticketclass.update

PATCH

/walletobjects/v1/eventTicketClass/{resourceId}

walletobjects.eventticketclass.patch

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Google Wallet API by hand means running the OAuth 2.0 flow for the wallet_object.issuer scope, refreshing tokens, and pointing at the walletobjects.googleapis.com host yourself. Through Jentic you install once, import the Google Wallet API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

The Google Wallet API puts the resource id in the URL path (/walletobjects/v1/eventTicketClass/{resourceId}), so a rule can pin your agent to one ticket class or object. You choose the operations it may call, so you can allow inserting and adding a message while an overwriting update like a full PUT is not included unless you add it.

Credential isolation

Your Google Wallet 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 an event ticket class' or 'issue a wallet pass object', and Jentic returns the matching Google Wallet API 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.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Google Wallet API through Jentic.

What authentication does the Google Wallet API use?

The Google Wallet API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I walletobjects.eventticketclass.insert with the Google Wallet API?

Yes. Use the POST /walletobjects/v1/eventTicketClass endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Google Wallet API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I walletobjects.eventticketclass.insert through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'walletobjects.eventticketclass.insert'. Jentic returns the matching Google Wallet API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Google Wallet API have?

The Google Wallet API exposes 98 endpoints covering walletobjects, eventticketobject, flightobject operations.

Can I limit what my agent is allowed to do with the Google Wallet API?

Yes. Because you run Jentic One yourself, your own rules decide which Google Wallet API operations and which stored OAuth credential the agent may use. You can allow narrow calls like inserting an event ticket class or adding a message while withholding an overwriting full PUT update unless you explicitly add it. Since the resource id sits in the URL path, such as /walletobjects/v1/eventTicketClass/{resourceId}, a rule can also pin the agent to a single ticket class or object.