Resy

Complete guide on our Resy module

Use Resy to watch restaurant reservation availability and attempt a booking. Monitor checks for openings; Reserve attempts to book them. Make sure the venue, party size and date range match what you actually want before starting Reserve tasks.

Reserve can book any available reservation within the selected date/time range. Only include a range you are willing to accept. There is no separate dining-time selector in the current task form.

Quick Start — Recommended Setup

1. Save your Resy account in Accounts and prepare a profile for Reserve mode.
2. Copy the restaurant’s full Resy venue URL and decide your party size and acceptable reservation dates.
3. Create a Resy Monitor task for that restaurant, party size and date range. Start with a 3000–5000 ms monitoring delay.
4. Create a Reserve task with matching details, select your saved account and configure a Captcha Provider. For ongoing availability checks, enable Watch Task and keep the matching Monitor running.
5. Start the tasks and watch their statuses. Confirm any successful reservation in your Resy account and confirmation message.

Preliminary Checklist

Prepare your profiles in Stellar. Reserve requires a profile; Monitor does not show a Profile field.

Save and test proxies before running. The Resy-specific guidance favors datacenter or ISP proxies for speed; residential proxies also work but continuous monitoring can use substantial data. Start with a small setup and test your own provider.

See Stella Proxies for the existing proxy resource.

Prepare your Resy account, the venue URL, party size and reservation date range. Configure the captcha method you plan to select in Reserve mode.

A cook group can help you find reservation-release information. Check venue details directly before running.

Accounts and Sessions

Adding Accounts

1. Open Accounts in Stellar 4.0.
2. Create or select a Resy account group.
3. Choose Add Account and enter the Resy account’s email and password, then save.
4. Select that saved account in the Reserve task. Adding credentials saves them; the task uses them to log in.

Mass Import Accounts

Use the account group’s Mass Import option for multiple accounts. Keep one account per line and use the format email;password. Follow the placeholder in the import window and check each entry before importing.

Example format: member@example.com;your-password. Replace both parts with your own account details; do not paste example credentials into live tasks.

Captcha Harvesters and Providers

Reserve mode requires a Captcha Provider. The current choices are Bot, Capsolver, Capmonster and Aycd. Monitor mode has no Captcha Provider field.

Choose Bot to handle challenges through Stellar captcha harvesters. Install Google Chrome, prepare a harvester and be ready to solve challenges when prompted.

Capsolver is a third-party solving service. Configure its key and available balance before selecting it.

Capmonster is another third-party solving service. Configure the matching key and balance first.

Aycd uses your configured AYCD AutoSolve connection. A valid key or connected service alone does not guarantee every challenge will solve.

Task Overview

Supported Modes

• monitor: checks reservation availability for the restaurant, party size and date range. It does not book the reservation by itself.
• reserve: attempts to book a reservation using your selected account and profile.

Monitor Mode

The screenshot below shows Resy Monitor mode in Stellar 4.0.

• Name: optional task label.
• Mode: select monitor.
• Monitor Proxy: the proxy group used to check availability.
• Restaurant URL: the full Resy venue link.
• Party Size: number of guests; the form starts at 2. This is separate from bottom Qty.
• Monitoring Delay: milliseconds between availability checks. The default is 3000 ms; the existing starting recommendation is 3000–5000 ms.
• Start Date / End Date: earliest and latest acceptable reservation dates. These describe the booking date range, not when Stellar starts or stops running.
• Reset Delay: delay before the monitor resets after detecting availability. Around 5000 ms is the existing starting recommendation.
• Start Time / End Time: optional task scheduling. These do not select your dining time.
• Qty at the bottom: number of task rows to create.

Reserve Mode

The screenshot below shows Resy Reserve mode in Stellar 4.0.

• Name: optional label.
• Mode: select reserve.
• Profile: choose the required profile for the booking task.
• Checkout Proxy: the proxy group used for the reservation attempt.
• Restaurant URL / Party Size: use the intended venue and guest count. Match the Monitor task when using Watch Task.
• Delay: current default 3000 ms. The existing starting recommendation is 3000–5000 ms; adjust for connection stability.
• Account: select the saved Resy account that should log in and book.
• Start Date / End Date: earliest and latest acceptable reservation dates. Match the monitor’s date range.
• Captcha Provider: Bot, Capsolver, Capmonster or Aycd.
• Watch Task: wait for a matching Monitor task to detect availability. With it off, Reserve checks availability independently.
• Presolve Captcha: solves ahead of the booking attempt. The current hint says the token is valid for 2 minutes, so solving far in advance can leave an expired token.
• Qty at the bottom: number of Reserve task rows, not party size.

Restaurant URL Example

Use the whole restaurant venue link, rather than a restaurant name or a product SKU. The original example is:

https://resy.com/cities/new-york-ny/venues/carbone

You can also obtain venue information from your cookgroup.

Monitor + Reserve Example

For a party of 2 at one restaurant, set the same Restaurant URL, Party Size = 2 and acceptable date range in both tasks. Enable Watch Task on Reserve. Start Reserve and Monitor; Waiting for Monitor Ping means Reserve is waiting for the monitor’s availability signal.

For a timed release, follow the release-specific instructions. A standalone Reserve task with Watch Task off does not need a Monitor task to trigger it.

FAQ

Does Monitor make a reservation?

No. Use Reserve for the booking attempt. A detected opening is not a confirmed reservation.

Is Qty the number of guests?

No. Party Size is the guest count. Qty at the bottom creates task rows. Start with one reservation setup so you can understand its behavior before adding more tasks.

Why is Reserve waiting for a monitor?

Watch Task is enabled. Keep a matching Monitor running, or turn Watch Task off if you intend Reserve to work independently.

For the earlier proxy reference, see Stella Proxies. Test your setup rather than assuming one proxy type always works.

Common Errors and Troubleshooting

• Login failure: verify the saved Resy credentials and the account selected in Reserve.
• No availability: check Restaurant URL, Party Size and the date range. The restaurant may not have released bookings or may have no matching openings.
• Waiting for Monitor Ping: confirm the monitor is running with matching restaurant, guest count and dates.
• Captcha not solving: check the selected provider’s setup and balance or Bot harvester readiness. If using Presolve, remember the 2-minute token lifetime.
• Connection errors or rate limiting: test another working proxy, reduce task count and increase delay. Residential monitoring can use considerable data.
• Availability detected but no reservation: an opening can disappear before the booking finishes. Check Resy for confirmation before treating the task as successful.

---