Lunchbox · Rate Limits

Lunchbox Rate Limits

The Lunchbox 2.0 Open API documentation (a Postman-published reference) states that the API uses standard HTTP status codes to indicate success or failure and that all schemas are JSON, but it does not publish specific per-second, per-minute, or daily request-rate numbers, nor documented rate-limit response headers. Access is provisioned per restaurant chain and authenticated with a team token (Authorization: Token ) for the Core, Management, and POS APIs, and with an Api-Key for the Loyalty API; enabling order webhooks requires coordination with the Lunchbox team. Concrete throttling limits are therefore established per integration partner via that onboarding process and are not reconciled here against a published limits page.

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

It captures 5 rate-limit definitions, measuring varies.

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

Tagged areas include Rate Limiting, Restaurant, Online Ordering, and Open API.

5 Limits Throttle: 429
Rate LimitingRestaurantOnline OrderingOpen API

Limits

Core API requests chain/token
varies
not publicly documented; provisioned per chain during onboarding
Authenticated with a team token scoped to the restaurant chain.
Management API requests chain/token
varies
not publicly documented; administrative throughput agreed with Lunchbox
Loyalty API requests merchant/key
varies
not publicly documented; scoped to the loyalty engine Api-Key
POS API order submission chain/pos-store
varies
not publicly documented; coordinated with the POS integration partner
Order webhooks chain/endpoint
varies
event-driven; delivery cadence coordinated with the Lunchbox team
Transaction, store-update, and order-update webhooks are enabled only after providing Lunchbox with a destination URL.

Policies

Token-Scoped Access
Limits and quotas are bound to the per-chain team token (Core, Management, POS) or the loyalty Api-Key, not to individual end users.
Partner Onboarding
Rate limits, webhook cadence, and POS throughput are negotiated and configured during partner onboarding rather than self-service.
Standard HTTP Semantics
Clients should treat 4xx/5xx responses with standard HTTP semantics and retry idempotent operations (GET, PUT, DELETE) with backoff on transient 5xx errors.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/lunchbox-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.