Resy API
Integuru generates a production-ready HTTP API for Resy, the restaurant reservation management platform. The integration covers 2 actions for venue listing and date-based reservation retrieval, both carrying richer docs, enabling restaurant tech teams to access reservation data programmatically.
2
Verified actions live today
<3 sec
Response latency per call
99.9%+
Reliability rate on generated APIs
24/7
On-call maintenance on Production plans
Integration facts
- Authenticates against
- https://os.resy.com/portal/login
- Authentication
- Login flows, including 2FA, handled by Integuru using your own Resy credentials.
- Approach
- Direct HTTP requests, with no browser automation or RPA involved.
Endpoints
Available actions
Don't see the action you need?
The actions above cover the most common Resy integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.
Guide
Resy integration guide
Last reviewed: July 2026
Overview
Integuru's Resy integration provides production-ready HTTP API access to Resy, the restaurant reservation management platform at os.resy.com, covering 2 actions: list_venues and get_reservations. Both actions carry richer documentation. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.
No public developer API. Resy OS does not expose an official developer API for reservation data retrieval. Restaurant tech teams that need reservation records programmatically for reporting, CRM sync, or operations pipelines have had no standard integration path.
Restaurant tech developers use list_venues to retrieve the venues on a Resy account and get_reservations to pull the reservation list for a specific venue and date. The venue_id from list_venues results feeds directly into get_reservations, making the two actions a natural pair. See the SpotOn integration or Aloha integration for other restaurant-tech integrations, or browse the full integrations catalogue.
Use Cases
Integuru's Resy integration covers the venue and reservation data workflows that restaurant tech teams need to automate.
- Venue listing: Call
list_venueswith no parameters to retrieve all venues associated with the authenticated Resy account. The results include each venue's numeric ID for use in reservation queries. - Reservation retrieval: Call
get_reservationswith requireddate(YYYY-MM-DD format) andvenue_id(integer, e.g. 77375) to retrieve all reservations for that venue on the specified date.
Setup Notes
Integuru's Resy integration authenticates against https://os.resy.com/portal/login. Configure credentials once during Integuru setup; Integuru handles session management automatically.
list_venues requires no parameters. get_reservations requires both date (YYYY-MM-DD) and venue_id (integer). Richer documentation for both actions is available via the Integuru dashboard after setup.
Guides in Restaurants & Food Service
Platform API guides in this vertical
Good to know
Before you start
- Can I use it today?
- Yes. Every action listed above has been verified against live Resy traffic. Install the CLI or sign in at app.integuru.com, connect your Resy account, and start calling the endpoints.
- What if Resy changes or breaks?
- On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
- What does it cost?
- Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.
FAQ