ItsaCheckmate · Rate Limits

Itsacheckmate Rate Limits

The ItsaCheckmate Marketplace for Developers API does not publish explicit per-second or per-minute request-rate numbers in its public reference. Access is governed primarily by short-lived scoped access tokens that expire after 24 hours by default and must be refreshed, and by a required location-activation gate before menu and order operations succeed. Limits below capture the documented token-lifecycle and access-control behavior; raw throughput limits are not documented and should be confirmed with Checkmate partner support.

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

It captures 3 rate-limit definitions, measuring varies.

The profile also includes 3 backoff/retry policies defined and response codes documented for unauthorized and forbidden.

Tagged areas include Rate Limiting, Point Of Sale, Online Ordering, and Integration.

3 Limits
Rate LimitingPoint Of SaleOnline OrderingIntegration

Limits

Access token lifetime token
varies
Access tokens expire 24 hours after issuance by default
Renew with the refresh_token grant before expiry; poll /oauth/token/info to check remaining lifetime.
Marketplace API request throughput account
varies
Not publicly documented — confirm with Checkmate partner support
No published per-second or per-minute request ceiling in the developer reference.
Menu and order access gate location
varies
Location must be activated (and verified for menus/orders) before access is granted
Calling menu or order operations before activation returns 401/403.

Policies

Token refresh
Use GET /oauth/token/info to determine remaining token lifetime and POST /oauth/token with grant_type=refresh_token to obtain a new access token before the 24-hour expiry.
Scoped access
Tokens are issued with specific scopes; the menus scope is required for Get Menu. Operations outside a token's scope return 403.
Activation prerequisite
Activate Location must be called first after token issuance; menu and order operations additionally require a verified location.

Sources