# Eat App Partner API > 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. - Canonical: https://www.anchorterminal.com/tools/eat-app - Markdown: https://www.anchorterminal.com/tools/eat-app.md (~6,250 tokens) - Slim: https://www.anchorterminal.com/tools/eat-app.min.md (~1,580 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/eat-app.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-14 ## Overview **Grade 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 | Field | Value | | --- | --- | | Vendor | Eat App (EAT APPLICATION DMCC) (https://restaurant.eatapp.co) | | Kind | HTTP API | | Category | Restaurant & local bookings (https://www.anchorterminal.com/categories/local-bookings) | | Transport | HTTP | | Endpoint | `https://api.eatapp.co/partners/v2` | | Auth | OAuth or key · Partner approval required for the Partner API. A booking channel asks to become a partner (info@eatapp.co), Eat App activates partnerships restaurant by restaurant, and its support team issues a long-term API key sent as a Bearer token. A login endpoint also exchanges the partner's email and password for a 24-hour token. Concierge API keys are created by Eat App for restaurant groups. The Restaurant MCP server uses OAuth with dynamic client registration, PKCE and a single `mcp` scope, and the restaurant signs in with its Eat App login. | | Pricing | Paid (Paid) · No per-call price. The pricing page marks API access in the Enterprise column only (Let's talk) and lists API and webhooks access as an add-on. Table management plans are $99, $199 and $389 a month, or $69, $159 and $299 billed yearly, with a 14-day trial and a $0 plan limited to 100 guests a month. The Restaurant MCP needs an active table management subscription. A sandbox host (api.eat-sandbox.co) is given to partners (https://restaurant.eatapp.co/pricing). | | x402 | No · No x402, MPP or L402 in the Partner or Concierge API docs, the MCP guide or the pricing page (checked 2026-10-14). | | Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | | Docs | https://documenter.getpostman.com/view/6173104/S1Lr4Av4 | | llms.txt | not found | | Last release | 2026-10-13 | | 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 | | Capabilities | booking.reservations, booking.availability, booking.venue, crm.records, events.webhooks-send | | Tags | hosted, closed-source, partner-only, rest, mcp, oauth, sandbox, status-page, webhooks, restaurants | | JSON | https://www.anchorterminal.com/api/v1/tools/eat-app.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-14 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 78 | 15.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 59 | 9.6 | | Agent ergonomics | 13% | 16.2 | 66 | 10.7 | | Security & auth | 14% | 17.5 | 43 | 7.5 | | Payments & pricing | 10% | 12.5 | 15 | 1.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 40 | 3.5 | | Transparency & trust (editorial 32, provenance 71) | 7% | 8.8 | 52 | 4.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **53.4 → D** | ### Why each score - Reliability 78: Graded as a hosted API. status.eatapp.co on Better Stack with separate Partner API, Concierge API and Restaurant API components and an incident page (20). In the 90 days to 14 October 2026 one incident, "Partner API and Concierge API are down", resolved on 12 August 2026 at 11:31 UTC. Its length isn't shown, but the page gives the Partner API 99.994 per cent uptime over 90 days, under ten minutes of downtime, so we read it as minor (20). 60 requests a minute on every endpoint (15). The 429 body is documented with a wait until the next minute, and Create Reservation takes an idempotency_token for safe retries, though no Retry-After header is documented (13 of 15). No SLA found (0). v2 is generally available (10). Total 78. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 59: No OpenAPI file. The Partner API (23 requests) and Concierge API (41 requests) are public Postman collections that download as JSON, with request bodies and example responses (12 of 25). No llms.txt or Markdown copies (0). Each request has a parameter table and notes on behaviour, such as legacy endpoints, the 24-hour include_tables limit and locked cancelled bookings, with little when-not-to-use guidance (12 of 20). Types, required flags and the reservation status list are given in tables rather than a schema (10 of 15). Example requests and responses, the JSON:API error format and named codes such as selected_tables_unavailable, but few per-endpoint error lists (10 of 15). v2 in the path and a dated changelog with entries from November 2023 to 13 October 2026 (15). Total 59. - Agent ergonomics 66: limit defaults to 30 with a maximum of 100, and table detail is opt-in through include_tables. No field selection (15). page and limit, with filters by restaurant, date, status and partner IDs (16). JSON:API error objects with codes, and a documented 429 body (12 of 20). idempotency_token on Create Reservation returns the earlier success for a repeat (18 of 20). No SDKs. A booking needs seven fields (5 of 15). Total 66. - Security & auth 43: 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 for a 24-hour token. The Restaurant MCP uses OAuth with dynamic client registration, PKCE, refresh tokens, a revocation endpoint and one `mcp` scope. No scoped API keys or rotation guidance were found (20 of 30). Partners see only restaurants whose partnership is active, Concierge calls are scoped by group and restaurant headers, and the MCP server is read-only (12 of 20). Responses carry guest notes and reviews written by people, with no injection guidance (3). The partner portal shows the reservations and guests a partner created, which gives some operator visibility (5 of 15). No security.txt on any Eat App host, and the trust centre at trust.eatapp.co loaded only its title, so no certification or disclosure programme was confirmed (3 of 20). Total 43. - Payments & pricing 15: No x402, MPP or L402 (0). Table management plan prices are public, but API access sits in the Enterprise column priced through sales (10 of 20). A $0 plan and a 14-day trial exist, and partners get a sandbox host, but whether either includes API or MCP access without a card was not established (5 of 20). A person applies for a partnership or signs in to approve the MCP connection (0). Total 15. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 40: The newest API changelog entry is 13 October 2026, adding table-level availability and table_ids on booking (30). Two dated entries in the last 90 days, 13 October and 21 July 2026, short of three (0). A dated changelog, a help centre and a support email, with no public issue tracker (10 of 15). No official SDKs (0). No package to assess (0). Total 40. - Transparency & trust 52: Closed service with public terms of service, effective 10 September 2025, entered into by EAT APPLICATION DMCC and referring to an agreement with its licensee Swiggy Limited (15 of 30). The privacy policy names the same entity, describes GDPR rights and says personal data is deleted or anonymised once its purpose ends, without fixed periods. No DPA was found (12 of 30). The old availability endpoint is marked legacy in the changelog, without a removal date (5 of 20). No subprocessor list or data locations were found, and the trust centre did not render for our reader (0). Total 32. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (17 items): https://www.anchorterminal.com/fixes/eat-app.md (JSON https://www.anchorterminal.com/fixes/eat-app.json) ### What we couldn't check - Which tools the Restaurant MCP exposes. The tool list needs a signed-in session and is not published - Whether a Partner API booking can carry a deposit or card guarantee, or how restaurants that require one handle API bookings - Which plans include API access. The pricing table marks only Enterprise, while the same page also lists API and webhooks access as an add-on - unchecked: the trust centre at trust.eatapp.co, which loads by script and showed only its title - unchecked: the registration date of eatapp.co, as RDAP did not answer - Coverage by country. The help centre names regions in the partner portal but no public list was found ### Sources - Partner API documentation and changelog (Postman): (seen 2026-10-14) - Concierge API documentation (Postman): (seen 2026-10-14) - Partner API guide: (seen 2026-10-14) - Concierge API guide: (seen 2026-10-14) - Restaurant MCP guide: (seen 2026-10-14) - MCP OAuth authorisation server metadata: (seen 2026-10-14) - status page and incident history: (seen 2026-10-14) - pricing: (seen 2026-10-14) - terms of service: (seen 2026-10-14) - privacy policy: (seen 2026-10-14) ## Who's behind it (provenance 71/100, checked 2026-10-14) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | EAT APPLICATION DMCC | 20/20 | | Domain age | eatapp.co, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | api.eatapp.co | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | status.eatapp.co | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of service (effective 10 September 2025) are entered into by EAT APPLICATION DMCC, Jumeirah Lake Towers, Dubai, licence DMCC-164040, and say the agreement also includes one executed with its licensee Swiggy Limited. The privacy policy names EAT APPLICATION DMCC and covers GDPR rights and a retention statement without fixed periods. The API changelog is a section of the Partner API Postman documentation. security.txt returns 404 on eatapp.co, restaurant.eatapp.co and api.eatapp.co. A trust centre at trust.eatapp.co loads by script and showed only its title to our reader. RDAP for eatapp.co did not answer, so the registration date is not recorded. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://restaurant.eatapp.co/terms), read 2026-10-14, dated 2025-09-10, states 6 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "In addition, you may not access the Platform and the services thereunder for purposes of monitoring their availability, performance or functionality, or for any other benchmarking or competitive purposes." - To know. Says access can be ended without notice or for any reason. "The continued availability of any services under the Platform shall be subject to Eat App’s consent, in its sole discretion, and to the fulfillment by the Subscriber of such conditions as Eat App may require from time to time." - Gives the date it was last updated. Last updated 2025-09-10. - Names the governing law or courts. The law of India. - States a limit on its liability. Capped at the fees paid in the 3 months before the claim. - Says how changes to the terms are announced. Gives thirty days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-14). Eat App may have independent access to Guest Information and other Subscriber Information, and the terms do not limit its right to use that information. "Eat App may have independent access to certain Guest Information of Subscriber or other Subscriber Information, and nothing in this Section 3.2 limits Eat App’s right to use such information." - Also in the text (2026-10-14). Eat App may list the subscriber as a client on its website and in marketing materials, using the subscriber's Restaurant Description. "Eat App may list Subscriber as a client on the Eat App website and marketing materials and may use the Subscriber’s Restaurant Description to do so consistent with Subscriber’s style guidelines." - Also in the text (2026-10-14). Eat App excludes liability for direct as well as indirect damages, including loss of data and loss of business. "EAT APP PARTIES ARE NOT, AND WILL NOT BE, LIABLE TO SUBSCRIBER FOR ANY DIRECT, INDIRECT, SPECIAL, PUNITIVE, EXEMPLARY, CONSEQUENTIAL, OR ANY OTHER DAMAGES WHATSOEVER" **Privacy policy** (https://restaurant.eatapp.co/privacy), read 2026-10-14, gives no date, states 6 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Says how long data is kept. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Live (updated 2026-10-14 09:41 UTC) - Right now: up, HTTP 404, 157 ms, checked 2026-10-14 09:41 UTC (get on `https://api.eatapp.co/partners/v2`) - Uptime 24h 100.0% (17 probes) · 30 days 100.0% (17 probes) · p50 175 ms · p95 322 ms - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/eat-app.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - idempotency_token on Create Reservation returns the first success for a repeated request - 60 requests a minute stated, with a documented 429 body - Better Stack status page with separate Partner API and Concierge API components and incident history - Dated API changelog, latest entry 13 October 2026 - Restaurant MCP server with OAuth dynamic client registration and read-only access ## Weaknesses - A booking channel can book only at restaurants whose partnership Eat App has activated - API access sits in the Enterprise column of the pricing page, priced through sales - No OpenAPI file, llms.txt or SDK, only Postman collections - A login endpoint accepts the partner's email and password for a 24-hour token - No security.txt, and the trust centre content did not load for our reader ## Before you call it (notes for agents) 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 First request: ```bash curl 'https://api.eat-sandbox.co/partners/v2/reservations' -H 'Authorization: Bearer API_TOKEN' -H 'Content-Type: application/json' -H 'Accept-Encoding: gzip' ``` Through letme (picks today, calling later): https://letme.dev/eat-app. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | TheFork B2B API | E | 43.6 | 951 | booking.reservations, booking.availability, booking.venue, crm.records, events.webhooks-send | no | https://www.anchorterminal.com/tools/thefork.md | | OpenTable APIs | E | 38.6 | 994 | booking.availability, booking.reservations, booking.venue, crm.records | no | https://www.anchorterminal.com/tools/opentable.md | | SevenRooms | F | 17.7 | 1043 | booking.venue, booking.reservations, booking.availability, crm.records | no | https://www.anchorterminal.com/tools/sevenrooms.md | | TableCheck API | C | 57.1 | 661 | booking.availability, booking.reservations, booking.venue | no | https://www.anchorterminal.com/tools/tablecheck.md | | Resy | F | 10.3 | 1068 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/resy.md | | Square Appointments (Bookings API) | B | 68.1 | 242 | booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/square-appointments.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Create Reservation takes an optional idempotency_token. A repeat returns the earlier success response instead of a second booking (source: ) - All endpoints are limited to 60 requests a minute, with a 429 and a many_requests code, and the limit can be raised (source: ) - The API changelog of 13 October 2026 added table-level availability (include_tables, covers) and table_ids on booking, and marked the old availability endpoint legacy (source: ) - The Restaurant MCP at https://api.eatapp.co/mcp/restaurants is read-only, covering reservations, guests, reviews and reports, and is set up from the MCP Servers page in Eat App (source: ) - The status page on Better Stack lists Partner API, Concierge API and Restaurant API separately, with one outage of the Partner and Concierge APIs on 12 August 2026 (source: ) - The Concierge API documents 41 requests for restaurant groups, scoped by X-Group-ID and X-Restaurant-ID headers (source: ) - #3 of 9 in Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md - All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md ## Compare - [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md): F 13.3 vs D 53.4 - [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md): D 53.4 vs E 38.6 - [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md): D 53.4 vs F 10.3 - [Eat App Partner API vs SevenRooms](https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.md): D 53.4 vs F 17.7 - [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md): D 53.4 vs C 57.1 - [Eat App Partner API vs TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md): D 53.4 vs E 43.6 - [Eat App Partner API vs Tock](https://www.anchorterminal.com/compare/eat-app-vs-tock.md): D 53.4 vs F 12.4 - [Eat App Partner API vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.md): D 53.4 vs B 68.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on eatapp.co or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "eat-app", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Eat App Partner API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Eat App Partner API on Anchor Terminal](https://www.anchorterminal.com/badges/eat-app.svg)](https://www.anchorterminal.com/tools/eat-app) ``` Plain link: ```html Eat App Partner API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Eat App Partner API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/eat-app-dark.png - Light: https://www.anchorterminal.com/assets/share/eat-app-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=eat-app