Eat App Rate Limits
Eat App's public API documentation states that endpoints are rate limited to approximately 60 requests per minute per API key. This applies to both the Partner API and the Concierge API. Requests are authenticated with a Bearer token (the issued API key) and scoped per group / per restaurant via headers, so throttling is effectively per credential. Beyond the request-rate cap, usage is bounded by the per-location plan (cover allowances) rather than by API quotas.
Eat App Rate Limits is the machine-readable rate-limit profile for Eat App on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and covers.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Restaurant, Reservations, Hospitality, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://restaurant.eatapp.co/knowledge/using-the-eat-app-partner-api-to-get-and-post-availability
- https://restaurant.eatapp.co/knowledge/using-the-eat-app-partner-api-to-get-and-post-availability-0
- https://documenter.getpostman.com/view/6173104/S1Lr4Av4
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/eat-app-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.