TableCheck · Rate Limits

Tablecheck Rate Limits

TableCheck publishes a fixed API rate limit of 10,000 requests per rolling 5-minute period, applied independently (non-fungible) to each API component - so you may send up to 10,000 requests to, for example, the Availability component and a separate 10,000 to the CRM component within the same 5-minute window. Exceeding the limit returns HTTP 429 Too Many Requests, and requests are refused until the next 5-minute period begins. TableCheck describes the limit as a hard maximum, not a service-level guarantee.

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

It captures 2 rate-limit definitions, measuring requests and items.

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

Tagged areas include Restaurant, Reservations, Rate Limiting, and Quotas.

2 Limits Throttle: 429
RestaurantReservationsRate LimitingQuotas

Limits

Per-Component Request Rate component
requests
10000 per 5 minutes
Applied independently to each API component; limits do not pool across components.
Pagination Page Size request
items
200 max per page (default 100)
List endpoints accept per_page up to 200 with a default of 100, paged by a zero-based page parameter.

Policies

Hard Cutoff
The published limit is a hard maximum, not an SLA. TableCheck may immediately suspend access if usage threatens platform stability, with re-enablement instructions to follow.
Backoff Strategy
On a 429 response, wait until the next 5-minute window and implement exponential backoff with jitter before retrying.

Sources