Rezku API
Rezku runs a REST API with webhooks, but only for ISV partners: no public developer portal, published reference, self-serve keys, or documented sandbox. Credentials come by emailing support@rezku.com, and operators report not all data tables are exposed, so most integrate via middleware.
Frequently asked questions
Rezku scores D+ on Supergood's API Report Card. Rezku runs a REST API with webhooks, but only for ISV partners: no public developer portal, published reference, self-serve keys, or documented sandbox. Credentials come by emailing support@rezku.com, and operators report not all data tables are exposed, so most integrate via middleware.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Rezku is a cloud-based restaurant management platform built by Guest Innovations (Sacramento, CA) covering point of sale, reservations and waitlist, online ordering, kitchen display systems, self-ordering kiosks, handheld/tableside ordering, inventory, loyalty, digital gift cards, text marketing, a website builder, and a payments-integrated merchant account (originally reselling Vantiv/Worldpay processing).
POS / Hospitality - specifically independent and small-to-mid-size multi-unit restaurants. Servers and bartenders use Rezku on iPads and handhelds to open and split checks, fire orders to kitchen displays or printers, apply modifiers/comps/voids, process EMV/NFC payments and tips, and clock in/out.
A recognized brand inside the restaurant POS long tail, present on every major review aggregator (Capterra, G2, GetApp, Software Advice, Sonary) and with 'thousands of restaurants nationwide' claimed on their site, but well behind Toast, Square, Clover, Lightspeed, and Aloha in installed base.
Yes - Rezku is the system of record for restaurant operations on its sites: real-time orders, checks and modifiers, EMV/NFC payments and tips, employee timecards and labor cost, menu/pricing, reservations and guest profiles, loyalty enrollment, gift card balances, and end-of-day sales/tax reporting.
~14 years old. Rezku was launched in 2012 by restaurateur Paul Katsch, with parent company Guest Innovations, Inc. formally incorporated in January 2015 in Sacramento, CA.
No public developer portal or documented API reference - integration credentials only available by emailing support@rezku.com. Not all data tables are exposed via the API, limiting analytics and data-warehouse use cases. Full sourced list under Sources below.
Common alternatives include Toast, Square for Restaurants, Lightspeed Restaurant, TouchBistro, SpotOn, Revel Systems. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Rezku MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Rezku doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.