Resy
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.
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.