# Resy Restaurants & Availability Scraper (`automation-lab/resy-restaurants-availability-scraper`) Actor

Search Resy restaurants and export public venue profiles, ratings, exposed menu links, and read-only date-and-party-size reservation availability.

- **URL**: https://apify.com/automation-lab/resy-restaurants-availability-scraper.md
- **Developed by:** [Stas Persiianenko](https://apify.com/automation-lab) (community)
- **Categories:** Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.72 / 1,000 restaurant extracteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

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

### Output example

```json
{
  "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

```bash
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

```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

```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:

```bash
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:

```json
{
  "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.

# Actor input Schema

## `searchQueries` (type: `array`):

Restaurant names, cuisines, neighborhoods, or city phrases, such as `pizza` or `French restaurants New York`. Terms influence Resy's relevance ranking and are not strict filters.

## `startUrls` (type: `array`):

Public resy.com venue URLs to extract. Slug-only venue URLs are supported.

## `venueIds` (type: `array`):

Optional numeric Resy venue IDs for direct extraction.

## `includeAvailability` (type: `boolean`):

Return read-only public slot times for each requested date and party size. This Actor never books a table.

## `availabilityDates` (type: `array`):

Up to 7 dates in YYYY-MM-DD format. Defaults to tomorrow when availability is enabled.

## `partySize` (type: `integer`):

Number of guests used for every availability check.

## `maxItems` (type: `integer`):

Maximum number of unique restaurant records to save.

## Actor input object example

```json
{
  "searchQueries": [
    "pizza"
  ],
  "venueIds": [],
  "includeAvailability": true,
  "partySize": 2,
  "maxItems": 10
}
```

# Actor output Schema

## `overview` (type: `string`):

Public Resy venue details and read-only availability observations.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQueries": [
        "pizza"
    ],
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("automation-lab/resy-restaurants-availability-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchQueries": ["pizza"],
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("automation-lab/resy-restaurants-availability-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQueries": [
    "pizza"
  ],
  "maxItems": 10
}' |
apify call automation-lab/resy-restaurants-availability-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automation-lab/resy-restaurants-availability-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JaYmWQMyLV6yORFFv/builds/oXCU51iyby4BInYKi/openapi.json