canonical: https://jentic.com/apis/getpocketpass.com/getpocketpass # Getpocketpass PocketPass Public API The PocketPass Public API lets an integrator read and write golfer records, house-account balances, and wallet-pass status for the golf merchants whose credentials they hold. Each customer has a house account whose balance summary and transaction history can be read, and new transactions can be posted against it. Wallet passes tied to those customers can be listed and read for their current status, and list endpoints are cursor-paginated. A bearer API key scopes every request to a single merchant. ## For AI agents Read and write golfer records, read house-account balances and transactions, post house-account transactions, and check wallet-pass status in PocketPass. Authenticates with a merchant-scoped bearer API key. ## Scope Does not process card payments, run tee-time booking, or issue the wallet passes themselves. Use for managing golfer records, house-account balances, and wallet-pass status only. ## Capabilities - Create and update golfer customer records for a merchant - Read a customer's house-account balance summary - List a customer's house-account transaction history - Post a transaction against a customer's house account - List and read wallet passes and their current status ## Use cases ### Agent-Posted House-Account Charges An AI agent connected through Jentic looks up a golfer's house-account balance and posts a transaction against it, so a charge or credit is recorded without a staff member keying it into the point-of-sale. Because the balance summary and transaction history share the same customer, the agent can read the current balance before it posts. Example prompt: Read this customer's house-account balance, then post a transaction against the account and confirm the new balance ### Golfer Onboarding and Wallet Pass A workflow creates a golfer customer record for a merchant and then reads the status of the wallet pass tied to that customer, so onboarding and the member's mobile pass stay in one flow. The wallet-pass status tells the agent whether the golfer's pass is active before relying on it. Example prompt: Create a golfer customer record, then look up the status of their wallet pass ### House-Account Statement Review A reconciliation workflow lists a customer's house-account transactions and reads the balance summary to review account activity, using cursor-based pagination to walk a long history. This gives an agent a read-only statement without opening the merchant dashboard. Example prompt: List this customer's house-account transactions and summarise them against the current balance ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/customers` | List customers | | POST | `/customers` | Create a customer | | GET | `/house-accounts/{customerId}` | Get a customer's house-account summary | | GET | `/house-accounts/{customerId}/transactions` | List a customer's transactions | | POST | `/house-accounts/{customerId}/transactions` | Post a transaction | | GET | `/wallet-passes` | List wallet passes | | GET | `/wallet-passes/{id}` | Get a wallet pass | ## Key resources - **Customers** — Golfer customer records that can be listed, created, read, and updated - **House Accounts** — Per-customer balance summaries and transaction histories, with transaction posting - **Wallet Passes** — Wallet passes tied to customers, listed and read for current status ## 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:** 42 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 17 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 67 / 100 - **View full report:** https://jentic.com/apis/getpocketpass.com/getpocketpass/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 ``` ## Why Jentic - **Setup:** Wiring the PocketPass API by hand means minting a merchant-scoped bearer key, carrying it on each request, and handling the cursor-based pagination on its list endpoints yourself. Through Jentic you install once, import PocketPass from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The PocketPass key is already scoped to a single merchant, and on top of that you choose which operations your agent may call. Allow reading customers and house-account balances while leaving transaction posting out, so posting a charge is not included unless you add it. - **Credential handling:** Your PocketPass API key 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 'read a house-account balance' or 'post a house-account charge', and Jentic returns the matching PocketPass operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Square Connect API** — Merchant platform with customer profiles, payments, and loyalty accounts - **Stripe API** — Card payment processing to collect the money that funds a house account ## FAQ ### Is there a PocketPass MCP server? You don't need an MCP server to give your agent the PocketPass API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can read house-account balances and post transactions straight away, with no extra server to run and no tool definitions to load into the agent's context. ### Can I limit what my agent is allowed to do with the PocketPass API? Yes. Write a rule that allows only the read operations the agent needs, such as reading customers and house-account balances, so it can review accounts without posting transactions. Posting a house-account transaction is a separate write operation that is not included unless you add it, and every call the agent makes is logged. ### What authentication does the PocketPass API use? The PocketPass API authenticates with a bearer API key sent in the Authorization header per its OpenAPI spec, and each key is scoped to a single merchant. Through Jentic the key is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs. ### Can I post a transaction to a customer's house account with the PocketPass API? Yes. You read the customer's house-account balance summary, then call the post-transaction operation to record a charge or credit against that account. You can list the account's transaction history, which is cursor-paginated, to confirm the posting. ### What are the rate limits for the PocketPass API? The OpenAPI spec does not specify rate limits for the PocketPass API. For current limits and key details, see the PocketPass documentation at https://pocketpass.golf. ### How do I post a house-account charge through Jentic? Import the PocketPass API from the Jentic API Directory, then have your agent issue a request such as 'post a charge to this golfer's house account'. Jentic matches the intent to the post-transaction operation and returns its input schema so the agent supplies the customer id and amount correctly, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.