Punchh
Punchh, now part of PAR Technology and offered under the PAR Engagement brand, is an enterprise loyalty, offers, and customer engagement platform for restaurants. It unifies guest data from online ordering, mobile apps, POS, and kiosks into a single view so brands can run personalized loyalty and marketing programs. PAR exposes well-documented Punchh APIs through its developer portal covering platform functions, mobile, online ordering, POS and kiosk integration, and a webhooks manager, with sample collections published to Postman. Most integration surfaces require partner certification. Over 275 restaurant brands rely on Punchh to grow customer lifetime value.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Punchh the way a machine reads it — 87 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Punchh scores 60.4/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Punchh
Each block below is one kind of artifact we hold for Punchh. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Punchh Check-In API
Loyalty check-ins for online orders.
Punchh Check-Ins API
Loyalty check-in transaction details.
Punchh Configuration API
Location and program configuration/metadata.
Punchh Offers API
Guest offer management.
Punchh Receipts API
Receipt detail storage.
Punchh Redemptions API
Apply rewards and discounts against online order receipts.
Punchh Users API
Guest registration, authentication, and profile management.
Scroll within the panel for all 7 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
PAR Punchh Mobile API
OPEN COLLECTIONPAR Punchh Online Ordering and SSO API
OPEN COLLECTIONPAR Punchh Platform Functions API
OPEN COLLECTIONPAR Punchh POS and Kiosk API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Punchh Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Punchh Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Punchh Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Loyalty Programs
Configurable points, rewards, tiers, and membership levels across channels.
Offers and Campaigns
Targeted offers, coupons, and personalized marketing campaigns driven by unified guest data.
Omnichannel Check-Ins
Earn loyalty across mobile, online ordering, POS, and kiosk channels.
Redemptions
Apply rewards, redeemables, and discounts against receipts with possible/create/void flows.
Webhooks Manager
Real-time event notifications for coupons, points, rewards, and guest lifecycle events.
Headless Offers
Surface Punchh-defined offers natively in external platforms via Platform Functions.
Semantic Vocabularies 4
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Punchh Mobile Context
JSON-LDPunchh Pos Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Punchh API Rules
SPECTRALPunchh API Rules
SPECTRALJSON Schema 15
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessToken
JSON SCHEMACreateUserRequest
JSON SCHEMALoginRequest
JSON SCHEMAMarkOffersReadRequest
JSON SCHEMATransactionDetailsRequest
JSON SCHEMATransactionDetails
JSON SCHEMAUpdateUserProfileRequest
JSON SCHEMAUserSession
JSON SCHEMAOnlineOrderCheckinRequest
JSON SCHEMAOnlineOrderCheckinResponse
JSON SCHEMAOnlineOrderRedemptionRequest
JSON SCHEMAOnlineOrderRedemptionResponse
JSON SCHEMARedeemable
JSON SCHEMAPosCheckinRequest
JSON SCHEMAPosUser
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 15
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Mobile Access Token Structure
JSON STRUCTUREMobile Create User Request Structure
JSON STRUCTUREMobile Login Request Structure
JSON STRUCTUREMobile Mark Offers Read Request Structure
JSON STRUCTUREMobile Transaction Details Request Structure
JSON STRUCTUREMobile Transaction Details Structure
JSON STRUCTUREMobile Update User Profile Request Structure
JSON STRUCTUREMobile User Session Structure
JSON STRUCTUREOnline Ordering Online Order Checkin Request Structure
JSON STRUCTUREOnline Ordering Online Order Checkin Response Structure
JSON STRUCTUREPlatform Functions Redeemable Structure
JSON STRUCTUREPos Pos Checkin Request Structure
JSON STRUCTUREPos Pos User Structure
JSON STRUCTUREScroll within the panel for all 15 ·
Examples 15
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Mobile Access Token Example
EXAMPLEMobile Login Request Example
EXAMPLEMobile User Session Example
EXAMPLEPos Pos User Example
EXAMPLEScroll within the panel for all 15 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Branded Mobile Loyalty App
Power a restaurant brand's mobile app with sign-in, profile, check-ins, and offers.
Online Ordering Rewards
Let guests earn and redeem loyalty on a digital ordering platform via SSO and check-in APIs.
POS Loyalty at the Counter
Look up guests, accrue points, and redeem rewards at the point of sale or kiosk.
External Offer Distribution
Pull Punchh redeemables into a CDP, messaging platform, or partner channel.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Point of Sale Systems
Integrations with restaurant POS platforms for in-store loyalty.
Online Ordering Platforms
Digital and online ordering platforms connect via the Online Ordering and SSO API.
Customer Data Platforms
Unify guest data with CDPs and CRMs.
Salesforce Marketing Cloud
Punchh Loyalty connector for Salesforce Marketing Cloud on AppExchange.
Messaging and Payment Gateways
Connects to messaging platforms, surveys, and payment gateways across dozens of categories.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Loyalty
Enterprise loyalty program management for restaurant brands.
Offers
Personalized offers and promotions engine.
Guest Engagement
Unified marketing and engagement across the guest lifecycle.
Resources
Every other property we hold for Punchh — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/punchh · machine-readable index on apis.io