Restaurant availability and reservation monitoring
Resyエンドポイントを使えば、「Restaurant availability and reservation monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Resy's public restaurant-reservation data into structured dining data -- restaurant profile and location detail with real-time bookable timeslots for a date/time and party size, ticketed dining event listings and full event detail with ticket packages, the cuisines present in a Resy city, and free-text restaurant search near a location. Credential-free.
Extract Resy restaurant profiles with live bookable timeslots, ticketed dining events, cuisines, and location-based restaurant search as structured JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
28
サンプル数
7
ライブカタログスナップショット
稼働エンドポイント
7
メソッド
GET
必須パラメータ
17
スキーマ参照
7
{
"platform": "Resy",
"endpoint": "resy-search",
"method": "GET",
"path": "/resy/search",
"auth": "apiKey"
}ユースケース
Extract Resy restaurant profiles with live bookable timeslots, ticketed dining events, cuisines, and location-based restaurant search as structured JSON.
Resyエンドポイントを使えば、「Restaurant availability and reservation monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Resyエンドポイントを使えば、「Ticketed dining event coverage」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Resyエンドポイントを使えば、「Cuisine and location-based restaurant discovery」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のResyエンドポイントカタログから取得しています（エンドポイント7件、ドキュメント化されたリクエストパラメータ28個、公開レスポンススキーマ7件）。DocsとPlaygroundが参照しているカタログと同じものです。
Resyのエンドポイントは7件、7つのリクエストファミリーに分類されています（Availability、Cuisines、Eventほか4件）。
これらのResyエンドポイントには28個のリクエストパラメータがドキュメント化されており、うち17個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
7件のResyエンドポイントのうち7件が実際のサンプルレスポンスを、7件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Resyのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、500、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Resyのエンドポイントは7個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/resy/availability
/resy/cuisines
/resy/event
/resy/events
/resy/locations
/resy/restaurant
エンドポイントカタログ
/resy/searchSearches restaurants by free-text term (name, cuisine, or neighborhood) near a latitude/longitude, optionally including live bookable-timeslot availability for a given date and party size. Credential-free.
MCPツール resy_search
/resy/restaurantReturns a restaurant's profile: name, cuisine, price tier, rating/review count, address/neighborhood, contact info, and description text. Credential-free.
MCPツール resy_restaurant
/resy/availabilityReturns the bookable reservation timeslots Resy currently shows for a restaurant, date, and party size -- the same read-only availability an anonymous visitor sees before signing in. This is discovery only; it does not create, hold, modify, or cancel a reservation.
MCPツール resy_availability
/resy/eventsReturns ticketed dining events (fixed-price, fixed-capacity experiences a restaurant hosts and sells tickets for, distinct from a regular reservation) in a Resy location. Credential-free, read-only discovery -- does not create, hold, or purchase a ticket.
MCPツール resy_events
/resy/eventReturns a ticketed dining event's full description, event-day instructions, and per-ticket-tier package breakdown (price, what's included, live ticket availability). All three identifiers come from a prior resy-events result: event_url_slug is that result's url_slug, restaurant_url_slug is its restaurant_url_slug, and location is the same city identifier resy-events was called with. Credential-free, read-only discovery -- does not purchase a ticket.
MCPツール resy_event_detail
/resy/cuisinesReturns the cuisines present among restaurants in a Resy location. Location is a short city code or numeric location id -- both already returned inline as location_code on resy-search and resy-restaurant results; there is no separate closed list of every valid location on Resy's own API, so this value always comes from a prior search/restaurant response rather than a guessed input.
MCPツール resy_cuisines
/resy/locationsReturns Resy's full list of operating locations (cities), optionally filtered by a free-text substring and/or country. This is the discovery source for the location value used throughout the rest of this family (resy-search's/resy-restaurant's location_code, resy-cuisines'/resy-events'/resy-event-detail's location). Credential-free.
MCPツール resy_locations
関連API
Travel & Hospitality
Build travel and lodging research workflows from structured Airbnb stay, room, availability, and review data.
Travel & Hospitality
Research hotels, restaurants, attractions, and destination pages from TripAdvisor with normalized listing and review endpoints.
Travel & Hospitality
Turn Expedia's Stays, Flights, and Things To Do results into structured JSON — destination search, hotel listings with pricing and reviews, flight offers, and activity search, sourced from the same API the official mobile app uses. Credential-free.
Resyのスクレイピング方法
Crawlora's Resy endpoints return restaurant profiles, live availability by seating area, ticketed dining events, cuisines, and Resy's operating cities as normalized JSON, with no account. Two things set Resy apart from other reservation sites here. Its timeslots are split by seating type, so the same 7pm table might be offered in both Dining Room and Patio. And /resy/events exposes ticketed experiences (tastings, prix-fixe dinners) that sell like tickets rather than reservations.
/resy/locations maps a name to Resy's location record. new york returns code ny, url_slug new-york-ny, coordinates, and a time_zone (EST5EDT). The code is what /resy/cuisines and /resy/events expect.
/resy/search takes a latitude, longitude, optional term, date, and party_size. It returns restaurants with cuisines, price_range, rating, neighborhood, and bookable timeslots. /resy/restaurant adds the address, cross_street, min and max party size, the website, and an about text.
/resy/availability returns every slot for a date and party size with start, end, seating_type, and min and max party size. On 2026-09-25, Eccolo in Hell's Kitchen offered 50 slots for two, split evenly between Dining Room and Patio. Group by seating_type to see outdoor capacity.
/resy/events requires a date as well as the location code. Without one, Resy rejects the request. ny on 2026-09-25 returned 402 events, each with a name, time and end_time, general_sale_date, party-size limits, and the hosting restaurant. /resy/event returns one event's full ticket packages.
FAQ
The request is missing date. Resy rejects an events query without it. Pass location as Resy's city code (ny, not new-york-ny) and a date.
Yes. Every slot from /resy/availability and /resy/search carries seating_type, such as Dining Room or Patio, with its own party-size limits.
/resy/cuisines returns the cuisine set for a location code. For ny: American, Chinese, Cocktail Bar, French, Italian, Japanese, Mediterranean, Mexican, New American, and Sushi.