Punchh · Rate Limits

Punchh Rate Limits

PAR Punchh does not publish public per-second or per-minute rate-limit numbers; the developer portal at developers.partech.com is partner-gated and exact throttling thresholds are shared with certified partners against sandbox and production environments. PAR states that integrated applications make roughly a billion API calls to Punchh each week in aggregate, indicating high-volume server-to-server usage, but this is a platform-wide figure, not a per-key limit. Limits below are descriptive placeholders pending confirmation from a certified-partner integration guide. Set reconciled to true only after verifying against PAR partner documentation.

Punchh Rate Limits is the machine-readable rate-limit profile for Punchh on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring varies.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Rate Limiting, Loyalty, and Restaurant.

4 Limits Throttle: 429
Rate LimitingLoyaltyRestaurant

Limits

Mobile API requests account/client
varies
partner-specific; not publicly documented
Scoped to the business OAuth client. Exact thresholds provided during partner certification.
Online Ordering and SSO API requests account/client
varies
partner-specific; not publicly documented
POS and Kiosk API requests location/business token
varies
partner-specific; not publicly documented
Scoped to the location token / business token pair.
Platform Functions API requests account
varies
partner-specific; not publicly documented

Policies

Authentication signing
All mobile and online-ordering calls must carry an HMAC-SHA256 x-pch-digest signature in addition to the bearer/client credential; unsigned or mis-signed calls are rejected before rate accounting.
Environment separation
Sandbox and production base URLs are issued separately by a PAR representative; load testing should target the sandbox environment.
Idempotency
Online-ordering check-ins and redemptions accept an external_uid / transaction identifier so retries do not double-count loyalty activity.
Raise limits via partnership
Higher throughput is negotiated through the PAR partner program rather than self-service.

Sources