Resy Restaurants & Availability Scraper

Search Resy restaurants and export public venue profiles plus read-only reservation availability for selected dates and party sizes. Use a restaurant, cuisine, neighborhood, or city phrase; paste real Resy venue URLs; or supply numeric venue IDs.

The Actor returns one typed row per restaurant. Each row can include ratings, cuisine, location, contact details, an exposed menu link, public images, collection membership, and slot times. It does not log in, book, hold, change, or cancel reservations.

What can this Resy scraper do?

• Search public Resy venue discovery by restaurant, cuisine, neighborhood, or location phrase.
• Resolve normal slug-based Resy venue URLs without asking users to find an internal ID.
• Fetch restaurant profile, contact, website, description, photos, and menu URL when Resy exposes them.
• Check up to seven dates for one party size in a run.
• Preserve zero-slot days so sold-out and not-yet-released observations remain useful.
• Produce JSON, CSV, Excel, XML, RSS, and API-ready dataset output through Apify.

Who is it for?

Hospitality analysts can compare restaurant supply across neighborhoods. Travel and dining teams can assemble curated venue datasets. Restaurant groups can monitor how their public profiles and slot supply appear. Researchers can schedule repeatable date-and-party-size snapshots without interacting with the booking flow.

Why use this Actor?

The workflow combines restaurant discovery, profile enrichment, and availability in one record. It uses Resy's public structured data instead of scraping fragile page text, keeps the extraction read-only, deduplicates restaurants by Resy venue ID, and stops at the requested maxItems limit.

What data is extracted?

Field	Meaning
venueId, name, url	Stable Resy identity and canonical venue page
city, region, country, neighborhood, address	Public location fields; unavailable values are null
latitude, longitude	Public venue coordinates when exposed
cuisines, priceRange	Cuisine labels and Resy price band
rating, ratingCount	Public rating summary when exposed
phone, website, menuUrl	Public contact links; menuUrl is not populated when Resy exposes no menu
description, needToKnow	Public profile copy
images, collections	Public image and editorial collection metadata
availability	Date, party size, slot count, times, and seating types
source, searchQuery, scrapedAt	Input provenance and observation timestamp

How much does it cost to scrape Resy restaurants?

Pricing has a $0.005 run start plus a tiered charge per restaurant saved. At the BRONZE tier, a restaurant costs $0.00620; higher Apify plan tiers receive lower per-record rates. Availability dates, menu links, and profile fields are included in the restaurant event and are not charged as separate record types.

Estimate a run as the active start price plus the BRONZE per-restaurant price multiplied by useful rows. For example, a 10-restaurant run uses one start event and 10 restaurant events. Charges apply only to accepted restaurant rows. Apify platform compute is billed according to your Apify plan.

How to get started

1. Open the Actor input page.
2. Enter at least one searchQueries, startUrls, or venueIds value.
3. Leave availability enabled or switch it off for profile-only extraction.
4. Set a party size and up to seven dates. If dates are omitted, the Actor checks tomorrow.
5. Set maxItems, then click Start.
6. Open the default dataset to inspect or export restaurant rows.

Input parameters

Input	Type	Default	Notes
searchQueries	string array	—	Names, cuisines, neighborhoods, and locations influence Resy's relevance ranking; they are not strict filters.
startUrls	request list	—	Public resy.com/.../venues/<slug> URLs.
venueIds	integer array	[]	Direct Resy venue IDs.
includeAvailability	boolean	true	Enables read-only slot checks.
availabilityDates	date string array	tomorrow	Maximum seven YYYY-MM-DD dates.
partySize	integer	2	From 1 to 20.
maxItems	integer	10	From 1 to 1,000 unique restaurants.

At least one search, URL, or ID input is required. Duplicate venues found through multiple inputs produce one row.

Input example

{
  "searchQueries": ["pizza"],
  "includeAvailability": true,
  "availabilityDates": ["2026-09-05"],
  "partySize": 2,
  "maxItems": 3
}

Output example

{
  "venueId": 59418,
  "name": "Brooklyn Ave Pizza Co.",
  "url": "https://resy.com/cities/los-angeles-ca/venues/brooklyn-ave-pizza-co",
  "city": "Los Angeles",
  "region": "CA",
  "cuisines": ["Pizza"],
  "rating": 4.52703,
  "ratingCount": 148,
  "menuUrl": "https://tr.ee/1H8qCFpMcl",
  "availability": [{
    "date": "2026-09-05",
    "partySize": 2,
    "slotCount": 109,
    "availableTimes": ["2026-09-05 11:00:00"],
    "seatingTypes": ["Dining Room"]
  }],
  "source": "search",
  "searchQuery": "pizza",
  "scrapedAt": "2026-09-01T20:15:00.000Z"
}

Times are source strings returned by Resy. A slotCount of zero means no public slots were returned for that date and party size; it does not predict future releases.

Monitoring workflows

Schedule the Actor daily or hourly with the same venue inputs, dates, and party size. Export each run to a database or automation flow, then compare slotCount, availableTimes, ratings, menu links, or profile text by venueId. The Actor emits observations; alerting and historical diff storage belong in the connected workflow.

Integrations and exports

Send dataset items to Google Sheets, Airtable, Make, Zapier, webhooks, cloud storage, or your own API. Use venueId as the durable join key and scrapedAt as the observation timestamp. The default dataset also supports CSV and Excel downloads directly from Apify Console.

Run through the Apify API

cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~resy-restaurants-availability-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQueries":["pizza"],"partySize":2,"maxItems":10}'

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/resy-restaurants-availability-scraper').call({
  searchQueries: ['pizza'],
  partySize: 2,
  maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient(token="YOUR_APIFY_TOKEN")
run = client.actor("automation-lab/resy-restaurants-availability-scraper").call(run_input={
    "searchQueries": ["pizza"],
    "partySize": 2,
    "maxItems": 10,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items

Use with MCP and AI assistants

Add the Actor to Claude Code:

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/resy-restaurants-availability-scraper"

Claude Desktop setup

Add this server in Claude Desktop's MCP configuration. Cursor setup and VS Code setup use the same HTTP server object in their MCP settings:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/resy-restaurants-availability-scraper"
    }
  }
}

Example prompts:

• "Search Resy for 10 pizza restaurants and return ratings and menu links."
• "Check the supplied Resy venue URL for a table for four on these two dates."
• "Export this Resy restaurant availability snapshot as CSV."

Limits and failure behavior

Search ordering is controlled by Resy and may include similarly named venues outside the phrase's apparent location. Use venue URLs or IDs for exact monitoring. Public fields vary by restaurant; absent menu, rating, address, or description values remain null or empty. Dates are limited to seven per run to keep requests bounded. The Actor retries temporary network, rate-limit, and 5xx failures up to three times, but fails visibly on invalid inputs or exhausted upstream errors.

Legality and responsible use

This Actor reads public restaurant and availability information. Review Resy's terms, applicable law, and your use case before collecting or redistributing data. Do not use the output to overload the source, misrepresent availability, or infer personal behavior. The Actor does not bypass account controls and does not make reservations.

Troubleshooting

Why did my query return a restaurant in another city?

Resy's relevance search can match a restaurant name before a location term, so query terms are not strict filters. Use exact venue URLs or IDs when location precision is required.

Why is menuUrl null?

Resy does not expose a menu link for every venue. Null means no menu URL appeared in the public profile response.

Why are there zero available slots?

The requested restaurant may be sold out, closed, outside its release window, or not returning public inventory for that date and party size. Try a later date, but do not treat zero as a permanent state.

FAQ

Does this Actor book tables?

No. It only reads public venue and slot information.

Can I search near me?

Use a city or neighborhood in searchQueries. The Actor does not use your device location.

Can I monitor several dates?

Yes. Supply up to seven availabilityDates; every restaurant row contains one availability object per date.

Are Resy Amex benefits included?

The Actor reports public venue and slot fields only. It does not authenticate, determine card eligibility, redeem Resy credits, or promise access to Amex Platinum or Global Dining Access inventory.

Related automation-lab Actors

Combine this Actor with other automation-lab restaurant and delivery-market tools when you need broader public menu or review research. Keep source-specific IDs separate and join only on defensible business keys such as canonical website and address.