Resy Availability Checker | Real-Time Reservation Slots (2026)

From Clearpath, creators of Resy Restaurant Scraper, OpenTable Availability and TheFork Restaurant Scraper. Restaurant discovery and reservation tools from the same team.

Why choose this actor?

Watch the restaurants you actually want. Check up to 10 Resy restaurant pages for your chosen date and party size. Get current reservation options without searching each restaurant by hand.

Get the time and the seating type. Each returned slot includes its start time, end time and seating type, such as Dining Room. Results also include the party size, slot count and check timestamp for your monitoring workflow.

Keep checking as availability changes. Schedule repeat runs in Apify and connect the results to your own alerts. Filter for returned slots before sending a notification to Slack, Telegram or another destination.

Quick start

Check available tables for two at Brooklyn Chop House today:

{
  "startUrls": [
    {
      "url": "https://resy.com/cities/new-york-ny/brooklyn-chop-house-downtown-fidi"
    }
  ],
  "partySize": 2
}

Omitting date uses today. Open actor input to choose another date, change the party size or add up to 10 restaurant URLs. Export JSON to preserve the reservation slots. Scheduled monitoring and notifications need to be configured separately; this actor checks availability and does not book tables.

Clearpath · Restaurant & Reservation Tools
Resy Slots You are here	Resy Places Restaurant leads	OpenTable Slots Available tables	TheFork Places Contacts & menus	TheFork Reviews Every language

Copy to your AI assistant

Copy this block into ChatGPT, Claude, Cursor, or any LLM to start using this actor.

clearpath/resy-availability-api on Apify. Call: ApifyClient("TOKEN").actor("clearpath/resy-availability-api").call(run_input={...}), then client.dataset(run["defaultDatasetId"]).list_items().items for results. Key inputs: startUrls (array, required: Resy restaurant URLs), date (string, YYYY-MM-DD), partySize (integer). Full actor spec (input schema with all params/enums/defaults, output dataset fields, README): GET https://api.apify.com/v2/acts/clearpath~resy-availability-api/builds/default (Bearer TOKEN) → inputSchema, actorDefinition.storages.dataset, readme. Pricing: $0.99 per 1,000 completed availability checks; each check covers one restaurant, date, and party size, including sold-out results. Failed checks have no availability-check charge. Platform usage included. Get token: https://console.apify.com/account/integrations

Quick Start

Check availability for tonight

{
    "startUrls": [
        { "url": "https://resy.com/cities/new-york-ny/carbone" }
    ],
    "partySize": 2
}

Monitor multiple restaurants for a specific date

{
    "startUrls": [
        { "url": "https://resy.com/cities/new-york-ny/carbone" },
        { "url": "https://resy.com/cities/new-york-ny/don-angie" },
        { "url": "https://resy.com/cities/new-york-ny/4-charles-prime-rib" }
    ],
    "date": "2026-03-15",
    "partySize": 4
}

Input Parameters

Parameter	Type	Description	Default
startUrls	array	Resy restaurant URLs to check (1-10). Must be venue pages, not city pages.	required
date	string	Date to check availability for (YYYY-MM-DD).	today
partySize	integer	Number of guests (1-20). Availability varies by party size.	2

URL format: Use restaurant pages like https://resy.com/cities/new-york-ny/carbone. City-level pages are not supported. Use the Resy Scraper for city-wide searches.

Output

Each successfully checked venue returns one result with nested time slots. Confirmed sold-out venues appear with slotCount: 0. Failed or unresolved checks are omitted and reported in the run log; they are never presented as sold out. Duplicate restaurant URLs in one run are checked once.

Output Example

{
    "venueId": 87134,
    "name": "Brooklyn Chop House - Downtown FIDI",
    "urlSlug": "brooklyn-chop-house-downtown-fidi",
    "url": "https://resy.com/cities/new-york-ny/brooklyn-chop-house-downtown-fidi",
    "date": "2026-03-06",
    "partySize": 2,
    "slotCount": 16,
    "slots": [
        {
            "startTime": "2026-03-06 12:00:00",
            "endTime": "2026-03-06 13:30:00",
            "type": "Dining Room",
            "token": "rgs://resy/87134/3533613/3/2026-03-06/2026-03-06/12:00:00/2/Dining Room",
            "configId": 1829819
        },
        {
            "startTime": "2026-03-06 17:00:00",
            "endTime": "2026-03-06 18:30:00",
            "type": "Dining Room",
            "token": "rgs://resy/87134/3533613/2/2026-03-06/2026-03-06/17:00:00/2/Dining Room",
            "configId": 1829819
        }
    ],
    "checkedAt": "2026-03-06T15:04:38.817580+00:00"
}

No Availability Example

{
    "venueId": 6194,
    "name": "Carbone",
    "urlSlug": "carbone",
    "url": "https://resy.com/cities/new-york-ny/carbone",
    "date": "2026-03-06",
    "partySize": 2,
    "slotCount": 0,
    "slots": [],
    "checkedAt": "2026-03-06T15:07:53.149031+00:00"
}

Pricing

$0.99 per 1,000 completed availability checks, on every Apify plan. Platform usage is included.

One check covers one restaurant, one date, and one party size, regardless of the number of available slots. A confirmed sold-out result counts as a completed check. Failed or unresolved checks have no availability-check charge.

Monitoring one restaurant for 30 days	Availability-check charges
Every 5 minutes (8,640 checks)	$8.55
Every minute (43,200 checks)	$42.77

Set a maximum run charge in Apify to control spending. The actor stops before checking another restaurant when the remaining budget cannot cover its result.

How to Monitor Resy Availability

The main use case: schedule this actor to run periodically and get notified when slots open.

1. Configure — Add your target restaurant URLs, set date and party size
2. Schedule — Create a schedule in the Apify console (every minute for hot restaurants, hourly for general monitoring)
3. Connect — Attach a webhook to get notified when runs complete. Connect to Slack, Discord, Telegram, Zapier, or your own endpoint

API Integration

Python

from apify_client import ApifyClient

client = ApifyClient("your_token")

run = client.actor("clearpath/resy-availability-api").call(run_input={
    "startUrls": [
        {"url": "https://resy.com/cities/new-york-ny/carbone"},
        {"url": "https://resy.com/cities/new-york-ny/don-angie"}
    ],
    "date": "2026-03-15",
    "partySize": 2
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    if item["slotCount"] > 0:
        print(f"{item['name']}: {item['slotCount']} slots available")
        for slot in item["slots"]:
            print(f"  {slot['startTime']} - {slot['type']}")

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'your_token' });

const run = await client.actor('clearpath/resy-availability-api').call({
    startUrls: [
        { url: 'https://resy.com/cities/new-york-ny/carbone' },
        { url: 'https://resy.com/cities/new-york-ny/don-angie' }
    ],
    date: '2026-03-15',
    partySize: 2
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.filter(i => i.slotCount > 0).forEach(item => {
    console.log(`${item.name}: ${item.slotCount} slots`);
});

Data Export

• JSON — Nested slot arrays fully preserved
• CSV — Flat fields, arrays serialized
• Excel — Spreadsheet-ready

FAQ

Q: How many restaurants can I check per run? A: Up to 10 restaurants per run. For bulk restaurant discovery, use the Resy Scraper.

Q: Do I need a Resy account? A: No. Availability data is fetched without authentication.

Q: What if a restaurant has no availability? A: It still appears in results with slotCount: 0 and slots: []. This confirms the check ran rather than silently skipping the venue.

Q: How current is the data? A: Real-time. Each run fetches live availability at the moment of execution.

Q: What are booking tokens? A: The token field in each slot is the Resy config token used to initiate a booking on the platform.

Q: Does party size affect results? A: Yes. Larger parties have fewer available slots since restaurants need to accommodate more seats.

Q: What happens with invalid URLs? A: Invalid or non-restaurant URLs are skipped with a warning. Valid URLs in the same batch still process normally.

Getting Started

1. Sign up for Apify — no credit card required
2. Open Resy Availability Checker
3. Paste a restaurant URL and click Start
4. Schedule recurring runs and attach webhooks for monitoring

Use with AI Assistants (OpenClaw, Claude, etc.)

Connect this actor to AI assistants via Apify's MCP server. Ask your assistant to check availability in natural language.

Setup

1. Go to mcp.apify.com and add clearpath/resy-availability-api to your MCP server
2. Connect the MCP server to your AI assistant (OpenClaw, Claude Desktop, Cursor, etc.)

OpenClaw example

Add Apify's MCP server to ~/.openclaw/openclaw.json:

{
  "provider": {
    "mcpServers": {
      "apify": {
        "command": "npx",
        "args": ["-y", "@apify/actors-mcp-server"],
        "env": {
          "APIFY_TOKEN": "your-apify-token"
        }
      }
    }
  }
}

Then message your OpenClaw bot on Telegram, WhatsApp, or Discord:

"Are there any openings at Carbone this Saturday for 2?"

"Check if Don Angie or 4 Charles has availability next Friday evening"

"Monitor Carbone for the next week, let me know if anything opens up"

The assistant calls the Availability Checker, interprets the results, and tells you exactly which time slots are open.

Legal Compliance

Extracts publicly available reservation data. Users must comply with Resy's terms of service and applicable data protection regulations (GDPR, CCPA).

Support

• Email: max@mapa.slmail.me
• Bugs: Issues tab on the Actor page
• Features: Email or issues

---

Real-time reservation monitoring for Resy restaurants.