Resy APIresy.com, opentable.com ↗
Search Resy restaurants by cuisine, location, and price range. Get ratings, availability, addresses, contact info, and editorial details via 2 clean endpoints.
What is the Resy API?
This API exposes 2 endpoints covering Resy venue data across major US cities. Use search_restaurants to find dining options by cuisine, neighborhood, price range, and party-size availability for a given date, returning up to 50 results per call. Use get_restaurant_details to pull a full venue record including address, phone, website, social handles, editorial description, and a detailed rating breakdown.
curl -X GET 'https://api.parse.bot/scraper/b3082859-cf6f-4594-835f-67c4ab52d109/search_restaurants?day=2026-07-14&limit=5&query=burger&sort_by=price&location=new-york&party_size=2' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace resy-com-opentable-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Resy restaurant search — find, compare, and inspect venues."""
from parse_apis.resy_restaurant_search_api import Resy, Sort, Location, RestaurantNotFound
client = Resy()
# Search for affordable sushi restaurants in New York, sorted by price.
for restaurant in client.restaurants.search(query="sushi", location=Location.NEW_YORK, sort_by=Sort.PRICE, limit=5):
print(restaurant.name, restaurant.price_range, restaurant.neighborhood)
# Drill into the first result for full details.
top = client.restaurants.search(query="italian", location=Location.SAN_FRANCISCO, sort_by=Sort.RATING, limit=1).first()
if top:
detail = top.details()
print(detail.name, detail.price_range, detail.description[:120])
print(detail.address.street, detail.address.locality, detail.address.region)
if detail.rating:
print(detail.rating.score, detail.rating.total_reviews)
# Fetch a known restaurant directly by slug.
try:
venue = client.restaurants.get(url_slug="le-bernardin")
print(venue.name, venue.type, venue.price_range)
print(venue.contact.website)
except RestaurantNotFound as exc:
print(f"Restaurant not found: {exc.url_slug}")
print("exercised: restaurants.search / summary.details / restaurants.get")
Full-text search over Resy venues in a geographic area. Returns restaurants with cuisine type, price range ($-$$$$), ratings, neighborhood, and available reservation time slots for the given day and party size. Results can be sorted client-side by price (cheapest first), rating (highest first), or left in default availability order. Paginates via limit (max 50 per call). Each result carries a url_slug usable with get_restaurant_details for full venue info.
| Param | Type | Description |
|---|---|---|
| day | string | Date for availability in YYYY-MM-DD format. Omitting defaults to tomorrow's date (UTC). |
| limit | integer | Maximum number of results (max 50). |
| query | string | Search query (e.g., 'burger', 'sushi', 'italian', 'restaurant'). |
| sort_by | string | Sort order for results. |
| location | string | City/area to search. Supported values include: 'new-york', 'los-angeles', 'chicago', 'san-francisco', 'washington-dc'. |
| party_size | integer | Number of guests for availability check. |
{
"type": "object",
"fields": {
"day": "string — the date used for availability (YYYY-MM-DD)",
"query": "string — the search query used",
"location": "string — the location searched",
"party_size": "integer — party size used",
"restaurants": "array of restaurant summary objects with venue_id, name, cuisine, price_range_id, price_range, neighborhood, locality, region, rating, review_count, url_slug, image, available_times, currency",
"total_results": "integer — total number of matching restaurants"
}
}About the Resy API
Search Restaurants
The search_restaurants endpoint accepts a free-text query (e.g., 'sushi', 'italian', 'burger'), a location slug such as 'new-york' or 'chicago', a day in YYYY-MM-DD format, and a party_size. When day is omitted, it defaults to tomorrow's date in UTC. Each result in the restaurants array includes venue_id, name, cuisine, price_range ($ through $$$$), neighborhood, locality, region, and available reservation time slots for the requested date and party size. Results can be sorted client-side by price or rating. The limit parameter caps results at a maximum of 50.
Restaurant Details
get_restaurant_details takes a url_slug obtained from search results — for example, 'le-bernardin' or 'nobu' — along with an optional location_slug in city-state format like 'new-york-ny'. The response includes a full address object with street, latitude, longitude, postal_code, and neighborhood; a contact object with phone, website, and menu_url; a social object mapping platform names to handles; a rating object with score, total_reviews, and scale; and a currency field. The image field returns a primary venue image URL.
Coverage and Scope
Location support includes major US markets: New York, Los Angeles, Chicago, San Francisco, Washington DC, and others accessible via the location slug parameter. Reservation availability data is tied to a specific day and party_size, so the same venue may return different time slots depending on those inputs. The venue_id and url_slug fields act as stable identifiers to link search results to detail records.
The Resy API is a managed, monitored endpoint for resy.com, opentable.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when resy.com, opentable.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, opentable.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?+
- Build a restaurant finder filtered by cuisine and price range for a specific city using
search_restaurants - Display real-time reservation availability for a given party size and date alongside restaurant ratings
- Compare restaurant price tiers across neighborhoods in a city using
price_rangeandneighborhoodfields - Populate a dining guide with editorial descriptions, images, and social media handles from
get_restaurant_details - Surface the highest-rated restaurants in a cuisine category by sorting on the
ratingresponse field - Show a venue's full contact details — phone, website, menu URL — in a local dining app
- Map restaurants geographically using
latitudeandlongitudefrom the address object in detail results
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Resy have an official public developer API?+
What availability data does search_restaurants return?+
day and party_size you specify. If you omit day, it defaults to tomorrow in UTC. Slots reflect availability at query time and will vary by date and party size. The endpoint does not book or hold reservations.Does the API cover menu items or dish-level data?+
menu_url in the contact object of get_restaurant_details, linking to the venue's menu page, but it does not return parsed menu items, dishes, or prices. You can fork this API on Parse and revise it to add a menu-parsing endpoint.Is coverage limited to US cities?+
location parameter currently supports a defined set of US metro slugs including 'new-york', 'los-angeles', 'chicago', 'san-francisco', and a few others. International Resy markets are not currently covered by this API. You can fork it on Parse and revise to extend the location list if Resy data is available in your target city.How does the url_slug relate to venue_id in the response?+
search_restaurants returns both url_slug and venue_id for each result. The url_slug is required as the primary input to get_restaurant_details, while venue_id is an integer identifier also present in the detail response. Use url_slug to chain calls between the two endpoints.