Resy
Resy is a restaurant reservation and discovery platform owned by American Express. Resy does not maintain a publicly self-serve developer portal; integration is restricted to approved partners (POS, CRM, loyalty, marketing, and discovery) under direct partnership agreements. The primary public surface is the consumer web and mobile app and an embeddable "Book with Resy" booking widget for restaurants. The unofficial internal client API at api.resy.com has been widely reverse-engineered by the community, but it is undocumented, unsupported, and may change without notice.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Resy the way a machine reads it — 21 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Resy scores 20.1/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Resy
Each block below is one kind of artifact we hold for Resy. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Resy Partner API
Partner-only REST API for reservations, availability, and restaurant metadata. Access is granted through Resy's partnerships team for approved POS, CRM, loyalty, and discovery i...
Resy Booking Widget
Embeddable "Book with Resy" booking button/widget that restaurants and partners can place on their own websites to drive reservations into Resy. This is the primary publicly ava...
Resy Internal Web/Mobile API (Undocumented)
Resy's web and mobile clients communicate with an internal API at api.resy.com. This API is not publicly documented or supported, requires credentials extracted from a logged-in...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Resy Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Resy Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Resy Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Reservation Management
Online table reservations, waitlists, and notify lists for diners and restaurants.
Restaurant Discovery
Editorial dining guides, curated lists (e.g. the Resy 100), and search across cities.
Resy OS
Restaurant-facing operating system for table, guest, and reservation management.
Booking Widget
Embeddable "Book with Resy" button restaurants place on their own sites.
Guest CRM and Notifications
Guestbook, guest communications, and reservation notifications.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 3
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Embed Reservations on a Restaurant Site
Add the "Book with Resy" booking button to a restaurant website to capture bookings.
Sync Reservations with POS and CRM
Approved partners synchronize reservation, guest, and reporting data with POS/CRM systems.
Discovery and Marketing Distribution
Surface restaurant availability through Resy and partner discovery channels.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
POS Systems
Toast, Square, Lightspeed, Aloha, Micros Simphony, Micros 3700, Heartland Xpient, Positouch, Squirrel, Lavu, Maitre D.
Events and Bookings
Tripleseat for private events and group bookings.
CRM and Guest Management
Loyalist, Fishbowl CRM, Bloom Intelligence.
Discovery and Distribution
Reserve with Google, MICHELIN, The Infatuation, Meta, Anthropic, Wine Enthusiast.
Analytics
Google Analytics.
Winery and eCommerce
WineDirect, Commerce7.
Resources
Every other property we hold for Resy — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/resy · machine-readable index on apis.io