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.
Resy is listed with 3 APIs on the APIs.io network. Tagged areas include Hospitality, Reservations, Restaurant, Dining, and Booking.
Resy’s developer surface includes developer portal, engineering blog, and 9 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/resy/"><img src="https://apis.io/badge/resy/card.svg" alt="Resy on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Machine-Readable Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
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...
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'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...
Resy API pricing
Not yet checked against Resy's own pricing page. Compiled by API Evangelist on 2026-05-08 from resy.com/; confirm before you rely on a figure.
aid: resy
url: https://raw.githubusercontent.com/api-evangelist/resy/refs/heads/main/apis.yml
name: Resy
kind: company
description: 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.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: low
source:
- plans
- security
generated: '2026-11-13'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/resy.png
tags:
- Hospitality
- Reservations
- Restaurant
- Dining
- Booking
tags_raw:
- Hospitality
- Reservations
- Restaurants
- Dining
- Booking
created: '2026-05-08'
modified: '2026-06-03'
specificationVersion: '0.23'
apis:
- aid: resy:partner-api
name: Resy Partner API
description: 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 integrations. No public developer portal or self-serve
signup; no public OpenAPI specification is published.
humanURL: https://resy.com/join/integrations/
tags:
- REST
- Partners
- Reservations
tags_raw:
- REST
- Partner
- Reservations
properties:
- type: Partners
url: https://resy.com/join/integrations/
- type: Contact
url: mailto:api@resy.com
- aid: resy:booking-widget
name: Resy Booking Widget
description: 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 available integration surface; it is a hosted widget rather
than a documented programmatic API.
humanURL: https://resy.com/join/integrations/
tags:
- Widgets
- Embed
- Reservations
tags_raw:
- Widget
- Embed
- Reservations
properties:
- type: Documentation
url: https://helpdesk.resy.com/en_us/booking-button-installation-Skx_7ueNo
title: Booking Button Installation
- aid: resy:internal-web-api
name: Resy Internal Web/Mobile API (Undocumented)
description: 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 session, and is subject to change without notice. The community
has reverse-engineered it; the libraries referenced below are unofficial and not affiliated with or endorsed by Resy.
humanURL: https://resy.com/
baseURL: https://api.resy.com
tags:
- Internal
- Undocumented
- Mobile
properties:
- type: CodeExamples
url: https://github.com/lgrees/resy-cli
title: resy-cli (Community, Unofficial - Go)
- type: CodeExamples
url: https://github.com/jeffknaide/resy-bot
title: resy-bot (Community, Unofficial - Python)
- type: CodeExamples
url: https://github.com/Alkaar/resy-booking-bot
title: resy-booking-bot (Community, Unofficial - Scala)
common:
- type: Website
url: https://www.resy.com/
- type: DomainSecurity
url: security/resy-domain-security.yml
- type: Portal
url: https://resy.com/
- type: Blog
url: https://blog.resy.com/
- type: Partners
url: https://resy.com/join/integrations/
- type: Contact
url: mailto:api@resy.com
- type: GitHubOrganization
url: https://github.com/resy
- type: LinkedIn
url: https://www.linkedin.com/company/resy-inc
- type: Plans
url: plans/resy-plans-pricing.yml
- type: RateLimits
url: rate-limits/resy-rate-limits.yml
- type: FinOps
url: finops/resy-finops.yml
- type: Features
data:
- name: Reservation Management
description: Online table reservations, waitlists, and notify lists for diners and restaurants.
- name: Restaurant Discovery
description: Editorial dining guides, curated lists (e.g. the Resy 100), and search across cities.
- name: Resy OS
description: Restaurant-facing operating system for table, guest, and reservation management.
- name: Booking Widget
description: Embeddable "Book with Resy" button restaurants place on their own sites.
- name: Guest CRM and Notifications
description: Guestbook, guest communications, and reservation notifications.
- type: UseCases
data:
- name: Embed Reservations on a Restaurant Site
description: Add the "Book with Resy" booking button to a restaurant website to capture bookings.
- name: Sync Reservations with POS and CRM
description: Approved partners synchronize reservation, guest, and reporting data with POS/CRM systems.
- name: Discovery and Marketing Distribution
description: Surface restaurant availability through Resy and partner discovery channels.
- type: Integrations
data:
- name: POS Systems
description: Toast, Square, Lightspeed, Aloha, Micros Simphony, Micros 3700, Heartland Xpient, Positouch, Squirrel, Lavu,
Maitre D.
- name: Events and Bookings
description: Tripleseat for private events and group bookings.
- name: CRM and Guest Management
description: Loyalist, Fishbowl CRM, Bloom Intelligence.
- name: Discovery and Distribution
description: Reserve with Google, MICHELIN, The Infatuation, Meta, Anthropic, Wine Enthusiast.
- name: Analytics
description: Google Analytics.
- name: Winery and eCommerce
description: WineDirect, Commerce7.
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Resy API — frequently asked questions
Does Resy have an API?
Yes. APIs.io lists 3 APIs from Resy, including Resy Partner API, Resy Booking Widget and Resy Internal Web/Mobile API (Undocumented).
How much does the Resy API cost?
APIs.io lists 2 pricing plans for Resy, with each plan's price, limits and inclusions under Pricing on this page.
Is the Resy API ready for AI agents?
Resy has a Kin Score of 12.0 out of 100 (emerging) and an Agent Readiness score of 1.9 (human-only), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.