Resy API
No documented public API. The consumer endpoints behind resy.com are reverse-engineered by community bots and can change at any time; using them requires lifting a session token, against ToS. Sanctioned integration is a booking widget or a private bilateral partner deal.
Frequently asked questions
Resy scores F on Supergood's API Report Card. No documented public API. The consumer endpoints behind resy.com are reverse-engineered by community bots and can change at any time; using them requires lifting a session token, against ToS. Sanctioned integration is a booking widget or a private bilateral partner deal.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Resy is a restaurant reservation marketplace and operator software platform.
POS / Hospitality - specifically restaurant reservations, table management, guest CRM and waitlist for full-service restaurants, bars, wineries and hotel F&B venues. Restaurants use Resy OS to: publish reservation availability across the Resy marketplace and on their own websites via embedded booking widgets, run table management and floor plans, manage waitlists, capture and segment guest profiles (tags, allergies, visit history, spend), enforce cancellation/no-show policies with stored cards, run pre-paid events and ticketed experiences (inherited from Tock), pull POS-integrated check data for spend analytics, sync guest lists out to marketing/CRM tools, and surface bookings to Amex card benefit programs.
High within urban fine/casual dining, moderate nationally. Pre-Tock-merger Resy had roughly ~12,000-16,000 venues; post-merger inventory pushes past 25,000. It is the dominant reservation app in NYC and a strong #2 to OpenTable nationally.
Reservations, waitlist entries, ticketed-experience bookings (post-Tock merger), guest profiles with PII (name, email, phone, tags, allergies, dietary preferences, visit/spend history, VIP and blocked flags, Amex cardholder linkage), stored payment cards for cancellation/no-show enforcement, POS-integrated check data and menu-item-level spend, floor plans and table inventory, marketing/email opt-ins, host/server notes.
Founded 2014, ~12 years old. Tech stack is modern web (React-style consumer app, REST/JSON APIs internally) and has been continuously invested in since the Amex acquisition.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Resy has partial MCP support. Resy does not publish an official MCP server. Multiple community MCP servers for Resy reservations exist, including one listed in the official MCP registry, but they rely on Resy's unofficial API.
Partially. MCP support for Resy exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.