SpotOn · Rate Limits

Spoton Rate Limits

SpotOn's developer APIs are key-scoped. The Restaurant POS Export API enforces request shape constraints rather than a published per-second rate: order and time-clock queries are limited to a 26-hour date range, paid in/out queries to a 7-day range, only data from roughly the last 90 days is retrievable, and end timestamps must be at least 5 minutes in the past. The Reserve API (SeatNinja) documents that the sandbox environment enforces daily and hourly request quotas while production has no documented rate limit. Numeric per-second limits are not published, so this artifact is not reconciled to specific figures.

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

It captures 3 rate-limit definitions, measuring varies and requests_per_hour.

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

Tagged areas include Rate Limiting, Restaurant, Point of Sale, and Reservations.

3 Limits Throttle: 429 Quota: 429
Rate LimitingRestaurantPoint of SaleReservations

Limits

Restaurant POS Export API requests (production) key/location
varies
no published per-second limit; constrained by date-range and lookback rules
Order, time-clock, and cash-deposit ranges max 26 hours; paid in/out ranges max 7 days; only ~90 days of history available; end timestamps must be at least 5 minutes in the past.
Reserve API requests (sandbox) key/restaurant
requests_per_hour
daily and hourly request quotas enforced; exact numbers not published
Sandbox-only quotas intended to protect the test environment.
Reserve API requests (production) key/restaurant
varies
no documented production rate limit

Policies

Per-key scoping
Each API key is scoped to specific locations (Restaurant API) or restaurants (Reserve API). Requests for resources outside the key's grant return 403 Forbidden; contact SpotOn to extend access.
Date-range windowing
Time-bounded export endpoints must be paged by walking the allowed window (26 hours for orders/time clock, 7 days for paid in/outs) across the ~90-day retention horizon rather than requesting a single large range.
Settlement delay
End timestamps must be at least 5 minutes in the past, giving the POS time to settle close-to-realtime data before it is exported.
Sandbox-first testing
Validate Reserve integrations against the sandbox (sandbox.seatninja.com), where hourly and daily quotas apply, before promoting to production.

Sources