Resy APIresy.com ↗
Search Resy restaurants, check real-time reservation slots, browse curated city lists, and get detailed venue profiles via a structured JSON API.
What is the Resy API?
The Resy API exposes 6 endpoints covering restaurant search, venue details, reservation availability, and curated city lists. search_restaurants returns paginated results with cuisine type, price range, rating, neighborhood, and live time slots for a given date and party size. get_restaurant_availability spans a full date range and can surface per-date slot details or a lightweight open/closed calendar — without making multiple individual requests.
curl -X GET 'https://api.parse.bot/scraper/d97a8bf9-e9ca-473c-b1e6-e66ada7210a0/search_restaurants?date=2026-10-09&page=1&query=italian&latitude=40.7128&per_page=5&longitude=-74.006&party_size=2' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over restaurants by keyword, location, date and party size, with the same controls the site's own browse page sends in its search request. Location is either a city (a Resy city slug such as new-york-ny or the city's display name such as 'New York', resolved to that city's map center and radius exactly as the site's /cities/<slug>/search page does; an unknown city returns a stale_input error) or, when city is omitted, a latitude/longitude center. cuisine is the site's structured cuisine facet (e.g. 'Cocktail Bar'), applied server-side and distinct from the free-text query; an unrecognised cuisine yields an empty result set. preferred_time is passed into the search request itself, so each returned restaurant's available_slots contains only slots at or near that time (the site's own near-time window, observed as roughly 45 minutes either side) and restaurants with nothing near that time are excluded; without it, available_slots lists the venue's bookable slots across the whole day. Returns paginated results with restaurant names, cuisine types, ratings, price ranges, neighborhoods, the venue's phone number (E.164 string such as +1XXXXXXXXXX as the site lists it, or null when the venue publishes none) and available reservation time slots for the queried date; each result carries a venue ID usable for detail/availability lookups. available_cuisines lists the cuisine facet values the site reports for the current result set (empty when a cuisine filter is applied). Paginates via the integer page counter with per_page results per page (max 50); pagination.total is the site's total for the query and total_pages the number of pages. Resolving a city costs one extra lookup per call; otherwise a call is a single request.
| Param | Type | Description |
|---|---|---|
| city | string | Resy city slug (e.g. 'new-york-ny', 'los-angeles-ca', 'miami-fl') or the city's display name (e.g. 'New York'), matched case-insensitively. When set, the search covers that city's own map center and radius and latitude/longitude are ignored. Omitting searches around latitude/longitude. |
| date | string | Date for availability check in YYYY-MM-DD format. Omitting defaults to today's date. |
| page | integer | Page number for pagination |
| query | string | Free-text search keyword typed into the site's search bar (e.g., 'italian', 'sushi', 'steakhouse'); empty returns all venues in the location |
| cuisine | string | Structured cuisine facet as shown in the site's Cuisines filter, e.g. 'Cocktail Bar', 'Italian', 'Japanese'; exact label, case-sensitive as the site lists it. The labels the site reports for a result set are returned in available_cuisines. Omitting applies no cuisine filter. |
| latitude | number | Latitude of search center (e.g., 40.7128 for NYC); ignored when city is set |
| per_page | integer | Results per page (max 50) |
| longitude | number | Longitude of search center (e.g., -74.006 for NYC); ignored when city is set |
| party_size | integer | Number of guests |
| preferred_time | string | Preferred dining time in the venue's local time, as 24h HH:MM (e.g. 20:00) or 12h like 8pm / 8:30pm; normalized to HH:MM in the response. Sent inside the search request so only venues with slots at or near this time are returned, each listing only those slots. Omitting returns venues with any availability on the date. |
{
"type": "object",
"fields": {
"city": "object or null: the resolved city when city was supplied (url_slug, name, code, country_code, time_zone, latitude, longitude, radius_meters of the search area)",
"date": "string, the date used for the search",
"query": "string, the search keyword used",
"cuisine": "string or null, the cuisine facet applied",
"pagination": "object with page, per_page, total, total_pages",
"party_size": "integer, the party size used",
"restaurants": "array of restaurant objects with id, name, cuisine, price_range, rating, neighborhood, region, url_slug, phone_number (string in E.164 form as the site lists it, or null when the venue publishes none), location, images, available_slots (start, end, type, token; limited to slots near preferred_time when set), need_to_know, tagline",
"preferred_time": "string or null, normalized HH:MM when supplied",
"available_cuisines": "array of cuisine facet labels the site reports for this result set (empty when cuisine is set)"
},
"sample": {
"data": {
"city": null,
"date": "2026-09-22",
"query": "italian",
"cuisine": null,
"pagination": {
"page": 1,
"total": 2500,
"per_page": 3,
"total_pages": 834
},
"party_size": 2,
"restaurants": [
{
"id": 92126,
"name": "Eccolo Italian Restaurant",
"images": [
"https://image.resy.com/3/003/2/92126/c4b61fbf0de87f66478b403dcc48c6ce6950c776/jpg/640x360"
],
"rating": {
"count": 123,
"average": 4.40164
},
"region": "NY",
"cuisine": [
"Italian"
],
"tagline": null,
"location": {
"latitude": null,
"longitude": null
},
"url_slug": "eccolo-italian-restaurant",
"price_range": 1,
"need_to_know": null,
"neighborhood": "Hell's Kitchen",
"phone_number": "+1 (555) 012-3456",
"available_slots": [
{
"end": "2026-09-22 17:30:00",
"type": "Dining Room",
"start": "2026-09-22 16:00:00",
"token": "REDACTED_TOKEN"
}
]
}
],
"preferred_time": null,
"available_cuisines": [
"Italian",
"Steakhouse",
"Spanish"
]
},
"status": "success"
}
}About the Resy API
Restaurant Search and Venue Discovery
search_restaurants accepts a keyword (query), optional latitude/longitude coordinates, a date in YYYY-MM-DD format, and a party_size. Results are paginated (up to 50 per page) and each restaurant object includes id, name, cuisine, price_range, rating, neighborhood, region, url_slug, and images, plus any available reservation slots for the queried date. The id and url_slug from these results feed directly into the detail and availability endpoints.
get_venue_info takes a url_slug and location slug (e.g., 'i-sodi' + 'new-york-ny') and returns the full venue profile: content blocks (about, need-to-know, tagline, why-we-like-it), contact details, images, collections, config flags, and cross-referenced IDs for Resy, Google, and Foursquare. get_restaurant_details focuses on a specific venue_id for a given date and party size, returning the slots array with each slot's start, end, type, token, size, and payment requirements.
Availability Calendars and Slot Lookup
get_restaurant_availability queries a venue over a date range (start_date to end_date) and returns a calendar array. Each entry has a date and inventory flags (reservation, event, walk-in). Setting include_slots: true or passing a preferred_time enriches each date entry with its bookable slot list and a time_filter object. The response also includes last_calendar_day, which reflects the venue's actual booking horizon — this may be shorter than the requested end_date.
find_venue_availability resolves a restaurant by name (word-based matching) and returns the matched venue object plus its slots in one call. Optional city, neighborhood, and preferred_time filters narrow results. If multiple venues match, the top match populates venue and the rest appear in other_matches. get_top_restaurants retrieves curated lists per city (city_slug) and list_type — top-rated, new, or trending — returning up to 50 venues with ratings, addresses, descriptions, images, and collection memberships.
The Resy API is a managed, monitored endpoint for resy.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when resy.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official resy.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Find open dinner reservations for a party of 4 at Italian restaurants in a given NYC neighborhood on a specific date
- Build a restaurant discovery feed for a city using
get_top_restaurantswith trending or new list types - Check a venue's booking horizon and full calendar availability before surfacing it to end users
- Resolve a restaurant name to a Resy venue ID and immediate slot list using
find_venue_availability - Display full venue profiles including about text, need-to-know notes, and images using
get_venue_info - Monitor availability windows across a date range to detect when hard-to-book restaurants open new slots
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Resy have an official public developer API?+
What does `get_restaurant_availability` return, and how does `include_slots` change the response?+
include_slots or preferred_time, the endpoint returns one entry per date between start_date and last_calendar_day, each with basic inventory flags (reservation, event, walk-in open/closed). Setting include_slots: true adds a full slots array to each available date, including start, end, type, token, size, and payment details. Passing preferred_time does the same but also populates a time_filter object with the normalized time.What is `last_calendar_day` and why might it differ from `end_date`?+
last_calendar_day reflects that venue-specific cutoff. If you request an end_date beyond the horizon, the calendar array stops at last_calendar_day. This means results for venues with short booking windows will be shorter than the requested range.Does the API expose menu data, user reviews, or past dining history?+
How does name matching work in `find_venue_availability`, and what if multiple venues match?+
name parameter must appear in the venue's name. Optional city and neighborhood filters narrow candidates further. The top-ranked match populates the venue field and its slots appear in slots. Any additional candidates are returned in other_matches, and total_matches gives the count of all candidates after filtering.