For 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.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PassEntry 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 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 instanceJentic 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.
What an agent can do with PassEntry API.
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
GET STARTED
Use for: I need to create a digital event ticket for Apple Wallet, I want to send a push notification to all loyalty cardholders, Issue a batch of 500 membership passes, Check whether a pass has been scanned at the venue
Not supported: Does not handle payment processing, event scheduling, or venue management — use for digital pass creation, distribution, and validation only.
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.
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
Patterns agents use PassEntry API for, with concrete tasks.
★ 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.
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.
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.
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.
Search Jentic for 'create a digital wallet pass', load the PassEntry pass creation schema, and execute with template ID and recipient details
38 endpoints — jentic publishes the only available openapi specification for passentry api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/api/v1/passes
Create a new digital pass
/api/v1/pass-templates
Create a pass template
/api/v1/passes/batch
Batch create multiple passes
/api/v1/passes/{id}/notification
Send push notification to a pass
/api/v1/scans
Record a pass scan event
/api/v1/loyalty/{id}
Update loyalty card points
/api/v1/batches/{id}
Check batch job status
/api/v1/webhook-subscriptions
Subscribe to pass lifecycle events
/api/v1/passes
Create a new digital pass
/api/v1/pass-templates
Create a pass template
/api/v1/passes/batch
Batch create multiple passes
/api/v1/passes/{id}/notification
Send push notification to a pass
/api/v1/scans
Record a pass scan event
Three things that make agents converge on Jentic-routed access.
Credential isolation
PassEntry Bearer tokens are stored encrypted in the Jentic vault. Agents receive authenticated request headers without token exposure, and webhook signatures are validated server-side.
Intent-based discovery
Agents search by intent (e.g., 'create a digital event ticket') and Jentic returns matching PassEntry operations with their request body schemas, including template ID requirements and recipient fields.
Time to first call
Direct PassEntry integration: 2-3 days for auth setup, template design API, and batch workflow implementation. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using PassEntry API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
/api/v1/loyalty/{id}
Update loyalty card points
/api/v1/batches/{id}
Check batch job status
/api/v1/webhook-subscriptions
Subscribe to pass lifecycle events