Restaurant availability and reservation monitoring
Usa los endpoints de Resy para convertir restaurant availability and reservation monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
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.
Familias de endpoints
6
Parámetros documentados
28
Ejemplos
7
Snapshot en vivo del catálogo
Endpoints activos
7
Métodos
GET
Parámetros obligatorios
17
Referencias de esquema
7
{
"platform": "Resy",
"endpoint": "resy-search",
"method": "GET",
"path": "/resy/search",
"auth": "apiKey"
}Casos de uso
Extract Resy restaurant profiles with live bookable timeslots, ticketed dining events, cuisines, and location-based restaurant search as structured JSON.
Usa los endpoints de Resy para convertir restaurant availability and reservation monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Resy para convertir ticketed dining event coverage en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Resy para convertir cuisine and location-based restaurant discovery en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Resy — 7 endpoints, 28 parámetros de solicitud documentados y 7 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
7 documented Resy endpoints, grouped into 7 request families — Availability, Cuisines and Event, plus 4 more.
28 request parameters are documented across those Resy endpoints, 17 of them required — the full input contract is public before you write any integration code.
7 of the 7 Resy endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
Resy endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
7 hosted MCP tools back the Resy endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
Estas tarjetas se generan a partir del catálogo de endpoints activo, así que la landing page refleja la misma superficie de API que usan Docs y Playground.
/resy/availability
/resy/cuisines
/resy/event
/resy/events
/resy/locations
/resy/restaurant
Catálogo de endpoints
/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.
Herramienta 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.
Herramienta 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.
Herramienta 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.
Herramienta 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.
Herramienta 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.
Herramienta 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.
Herramienta MCP resy_locations
APIs relacionadas
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.
Cómo hacer scraping de 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.
Preguntas frecuentes
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.