canonical: https://jentic.com/apis/passentry.com/passentry

# PassEntry API

Jentic publishes the only available OpenAPI specification for PassEntry API, keeping it validated and agent-ready. The PassEntry API enables creation and management of digital passes for Apple Wallet and Google Wallet, covering event tickets, loyalty cards, boarding passes, and membership credentials. It provides 38 endpoints for pass template design, individual and batch pass issuance, NFC reader configuration, scan validation, wallet push notifications, and webhook-based lifecycle events.

## For AI agents

Create and manage digital wallet passes for Apple Wallet and Google Wallet. Issue event tickets, loyalty cards, and membership passes individually or in batches, with NFC scanning and push notification support.

## Scope

Does not handle payment processing, event scheduling, or venue management - use for digital pass creation, distribution, and validation only.

## Capabilities

- Design pass templates with custom fields and visual layouts
- Issue individual passes or batch-create thousands simultaneously
- Send push notifications directly to passes in user wallets
- Configure NFC readers for contactless pass scanning and validation
- Track scan events with timestamps and reader location data
- Manage loyalty program passes with point balances and tier updates
- Subscribe to webhook events for pass install, uninstall, and scan lifecycle

## Use cases

### Event Ticketing with Digital Passes

Create and distribute digital event tickets directly to attendees' Apple Wallet or Google Wallet through the PassEntry API. Design a pass template with event branding, issue individual passes with unique barcodes or QR codes, and validate entry using NFC readers or scan endpoints. Each pass supports real-time updates for gate changes, time modifications, or cancellation notices pushed directly to the wallet.

Example prompt: Create a pass template for 'Summer Concert 2026' via POST `/api/v1/pass-templates`, then issue a pass for attendee email user@example.com via POST `/api/v1/passes` with the template ID

### Loyalty Card Program Management

Issue digital loyalty cards that live in customers' mobile wallets and update in real time as points accumulate or tier status changes. The PassEntry API provides dedicated loyalty endpoints for reading and updating point balances, plus push notifications to alert cardholders of rewards milestones. Eliminates physical card production and enables instant program enrollment at point of sale.

Example prompt: Retrieve loyalty pass details via GET `/api/v1/loyalty/{id}`, update the points balance via PATCH `/api/v1/loyalty/{id}`, then send a notification via POST `/api/v1/passes/{id}/notification`

### Batch Pass Issuance for Large Events

Generate hundreds or thousands of unique digital passes in a single batch operation using the PassEntry API. Upload attendee data, specify the template, and monitor batch job progress through status endpoints. Each pass receives a unique identifier and barcode, and the batch can be cancelled mid-processing if needed. Suitable for conference registration, stadium events, or membership renewals.

Example prompt: Submit a batch pass creation job for 200 attendees via POST `/api/v1/passes/batch` with the template ID and attendee data, then check status via GET `/api/v1/batches/{id}`

### AI Agent Pass Management via Jentic

AI agents issue and manage digital wallet passes through Jentic without handling Bearer token authentication directly. Jentic stores the API key securely and provides operation discovery by intent, letting agents create passes, send notifications, or check scan status by describing what they need. This eliminates the need to read PassEntry documentation or manage token headers manually.

Example prompt: Search Jentic for 'create a digital wallet pass', load the PassEntry pass creation schema, and execute with template ID and recipient details

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/passes` | Create a new digital pass |
| POST | `/api/v1/pass-templates` | Create a pass template |
| POST | `/api/v1/passes/batch` | Batch create multiple passes |
| POST | `/api/v1/passes/{id}/notification` | Send push notification to a pass |
| POST | `/api/v1/scans` | Record a pass scan event |
| PATCH | `/api/v1/loyalty/{id}` | Update loyalty card points |
| GET | `/api/v1/batches/{id}` | Check batch job status |
| POST | `/api/v1/webhook-subscriptions` | Subscribe to pass lifecycle events |

## Key resources

- **Pass Templates** — Create, list, and update pass template designs
- **Passes** — Issue, update, and manage individual digital passes
- **Batches** — Create and monitor bulk pass issuance jobs
- **Loyalty** — Read and update loyalty card point balances
- **Scans** — Record and retrieve pass scan events
- **Readers** — Configure NFC readers for pass validation
- **Webhook Subscriptions** — Subscribe to pass lifecycle events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 41 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/passentry.com/passentry/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the PassEntry API by hand means learning its bearer token auth and webhook signature header, setting the api.passentry.com host, and building batch and notification handling yourself. Through Jentic you install once, import PassEntry from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** PassEntry puts the pass id in the URL path (`/api/v1/passes/{id}/...`), so a rule can pin your agent to a named pass for actions like sending its notification. You choose the operations it may call, so creating passes, batch creation, or webhook subscriptions are not included unless you add them.
- **Credential handling:** Your PassEntry bearer token 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 a digital event pass' or 'send a pass notification', and Jentic returns the matching PassEntry operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Google Wallet Passes API** — Google's native API for creating and managing Google Wallet passes
- **Ticketmaster Discovery API** — Event discovery and ticketing marketplace for sourcing event data
- **Mailchimp API** — Email marketing for loyalty program communications

## FAQ

### Why is there no official OpenAPI spec for PassEntry API?

PassEntry does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PassEntry API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the PassEntry API use?

The API uses Bearer token authentication for standard operations (passed in the Authorization header) and a separate X-Webhook-Signature header for verifying incoming webhook payloads. Through Jentic, Bearer tokens are stored encrypted and agents authenticate without exposing tokens in their context.

### Can I create passes for both Apple Wallet and Google Wallet?

Yes. The PassEntry API generates passes compatible with both Apple Wallet and Google Wallet from a single pass template. You design the template once and the platform handles format conversion for each wallet type.

### How do I send a push notification to a pass holder?

Call POST `/api/v1/passes/{id}/notification` with the notification content in the request body. The message is delivered directly to the pass in the user's wallet app. You can also send wallet-level messages via POST `/api/v1/entities/{entity_id}/messaging/wallet.`

### What is the batch pass creation limit?

The API supports batch creation via POST `/api/v1/passes/batch` and batch updates via POST `/api/v1/passes/batch/update.` Monitor job progress with GET `/api/v1/batches/{id}.` Specific batch size limits depend on your PassEntry plan tier.

### How do I validate a pass scan through Jentic?

Search Jentic for 'record pass scan event' to find the POST `/api/v1/scans` operation. Load the schema to see required fields (pass ID, reader ID, timestamp), then execute. You can also retrieve scan history via GET `/api/v1/scans.` Install with pip install jentic.

### Can I limit what my agent is allowed to do with the PassEntry API?

Yes. Because you run Jentic One yourself, your own rules decide which PassEntry operations and credentials the agent may use, so it can only call the endpoints you explicitly grant. You choose the operations it may run, meaning creating passes via POST `/api/v1/passes`, batch creation via POST `/api/v1/passes/batch`, or webhook subscriptions are excluded unless you add them. Since PassEntry puts the pass id in the URL path, such as `/api/v1/passes/{id}/notification`, a rule can also pin the agent to a single named pass for actions like sending its push notification.