# Eat App Partner API (slim)

> Eat App is a restaurant reservation and table management system. Its Partner API lets booking channels check availability and create, change and cancel reservations, a Concierge API serves restaurant groups, and a read-only Restaurant MCP server connects AI assistants.

- Full: https://www.anchorterminal.com/tools/eat-app.md (~6,250 tokens) · this version ~1,580 tokens · JSON https://www.anchorterminal.com/tools/eat-app.json · canonical https://www.anchorterminal.com/tools/eat-app
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-14

**D · 53.4/100 · rank #752 of 1076 · #3 in Restaurant & local bookings · not agent-ready · confidence medium**


Assessment: A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.

## Facts

- Kind: HTTP API · vendor: Eat App (EAT APPLICATION DMCC) · category: Restaurant & local bookings · legal entity: EAT APPLICATION DMCC · provenance 71/100
- Endpoint: `https://api.eatapp.co/partners/v2` (HTTP)
- Auth: OAuth or key · pricing: Paid · x402: no · licence: Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements
- Probe metrics: not measured yet (probes haven't run)
- Surface graded: The Partner API (v2) for booking channels, with the Concierge API and the Restaurant MCP server read as related surfaces
- Diner or venue: Partner API acts for the diner through a booking channel. Concierge API and Restaurant MCP act for the restaurant or group
- Partner API endpoints: 23 requests. Authentication, profile, partnered restaurants, regions, cuisines, neighbourhoods, consumer restaurants, experiences, promotional groups, availability range, reservations (list, show, create, update), guests and tables
- Booking rules: Availability within the next 30 days. Create needs restaurant_id, start_time, covers, first and last name, phone and email. Update can set status to late or canceled, and a cancelled booking cannot change
- Credentials: Long-term Bearer API key from Eat App support, or a 24-hour token from partner email and password. MCP uses OAuth with dynamic registration, PKCE, refresh and revocation endpoints
- Environments: Sandbox at https://api.eat-sandbox.co and production at https://api.eatapp.co, with a partner portal for each
- Rate limits: 60 requests a minute on every endpoint, adjustable on request. 429 with a many_requests code (Partner) or too_many_requests (Concierge)
- Errors: HTTP status codes with JSON:API error objects, for example 422 selected_tables_unavailable
- Deposits: Create and show return payment details when a payment exists (changelog, 2 July 2025). No deposit or card field on the Partner API booking request was found
- Status: status.eatapp.co on Better Stack, components Server, RealTime Server, Partner API, Concierge API and Restaurant API

- Scores: Reliability 78, Performance pending, Schema & documentation 59, Agent ergonomics 66, Security & auth 43, Payments & pricing 15, Task success pending, Maintenance & community 40, Transparency & trust 52 · total over the 7 assessed categories
- Why: Reliability, Graded as a hosted API. · Schema & documentation, No OpenAPI file. · Agent ergonomics, limit defaults to 30 with a maximum of 100, and table detail is opt-in through include_tables. · Security & auth, The Partner API uses a long-term Bearer key issued by Eat App support, and a login endpoint also accepts the partner's email and password fo… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, The newest API changelog entry is 13 October 2026, adding table-level availability and table_ids on booking (30). · Transparency & trust, Closed service with public terms of service, effective 10 September 2025, entered into by EAT APPLICATION DMCC and referring to an agreement…
- Sources: 10, open questions: 6, both in the full twin
- Capabilities: booking.reservations, booking.availability, booking.venue, crm.records, events.webhooks-send
- JSON: https://www.anchorterminal.com/api/v1/tools/eat-app.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/eat-app.svg` or a link to https://www.anchorterminal.com/tools/eat-app from a page on eatapp.co or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Send a unique idempotency_token with each new booking so a retry returns the first result
2. Use POST /partners/v2/availability/range, not the legacy availability endpoint
3. Keep include_tables ranges to 24 hours or less and pass covers with it
4. Stay under 60 requests a minute and wait for the next minute after a 429
5. Cancel by PATCH with status canceled, after which the reservation can no longer change

## Connect

```bash
curl 'https://api.eat-sandbox.co/partners/v2/reservations' -H 'Authorization: Bearer API_TOKEN' -H 'Content-Type: application/json' -H 'Accept-Encoding: gzip'
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/eat-app

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| TheFork B2B API | E | 43.6 | booking.reservations, booking.availability, booking.venue, crm.records, events.webhooks-send | https://www.anchorterminal.com/tools/thefork.min.md |
| OpenTable APIs | E | 38.6 | booking.availability, booking.reservations, booking.venue, crm.records | https://www.anchorterminal.com/tools/opentable.min.md |
| SevenRooms | F | 17.7 | booking.venue, booking.reservations, booking.availability, crm.records | https://www.anchorterminal.com/tools/sevenrooms.min.md |
| TableCheck API | C | 57.1 | booking.availability, booking.reservations, booking.venue | https://www.anchorterminal.com/tools/tablecheck.min.md |
| Resy | F | 10.3 | booking.reservations, booking.availability, booking.venue | https://www.anchorterminal.com/tools/resy.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)