canonical: https://jentic.com/apis/walletobjects.googleapis.com/walletobjects-googleapis

# Google Wallet API

API for issuers to save and manage Google Wallet Objects. The API exposes 98 endpoints secured with oauth2 authentication.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- walletobjects.eventticketclass.insert
- walletobjects.eventticketclass.list
- walletobjects.eventticketclass.get
- walletobjects.eventticketclass.update
- walletobjects.eventticketclass.patch
- walletobjects.eventticketclass.addmessage
- walletobjects.eventticketobject.insert

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **walletobjects** — Operations related to walletobjects
- **eventticketobject** — Operations related to eventticketobject
- **flightobject** — Operations related to flightobject
- **genericobject** — Operations related to genericobject
- **transitclass** — Operations related to transitclass

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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