Resy venue with open tables

GET https://api.api.sh/resy/v1/venue
1 credit / call food & delivery try it in the playground →

One Resy venue for a date and party size: id, name, link, cuisine, price band, average ticket, currency, timezone, rating and count, address, city, region, postal code, country, neighbourhood, cross streets, coordinates, phone, website, menu link, Instagram and Facebook, about / why we like it / need to know texts, description, restaurant group, party-size limits and large-party message, Global Dining Access flag, awards, collections; the day's open slots (time, end, seating type, party range, deposit, duration in minutes, tables free), notices; menu_highlights (signature dishes), booking_policy (deposit, service charge, cancellation fee, cancellation and change cut-offs, large-party rules), turn_times (table time by party size), images_full (full-size photos), special_announcement, average_ticket_label, tax_included; the calendar of the next year's days (reservation, event, walk-in status) and upcoming events with prices.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
url string The venue's resy.com/cities/<city>/venues/<slug> link (from /resy/v1/search). Example: https://resy.com/cities/new-york-ny/venues/carbone
city string City slug (with slug) instead of url. Example: new-york-ny
slug string Venue slug (with city). Example: carbone
date string Date YYYY-MM-DD for the slots (default tomorrow).
seats integer Party size, 1-20 (default 2). Example: 2

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/resy/v1/venue?url=https%3A%2F%2Fresy.com%2Fcities%2Fnew-york-ny%2Fvenues%2Fcarbone" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.