Rezku API
Rezku is a cloud-based restaurant management and iPad point-of-sale platform spanning ordering, kitchen, inventory, loyalty, gift cards, and reporting for independent and multi-location restaurants, bars, and pizzerias. With no documented public developer API, an unofficial API lets you programmatically pull orders, checks, menu items, payments, inventory, labor, and reporting data—and push updates like menu changes and order events back into Rezku.
What is Rezku?
Rezku is a cloud-based restaurant management system built around an iPad point of sale, combining front-of-house ordering with back-office operations for independent and multi-location restaurants, bars, breweries, pizzerias, quick-service, fast-casual, and food trucks. Restaurants use Rezku to ring up checks, run online and tableside ordering, manage kitchen displays and inventory, schedule and clock staff, pool tips, run loyalty and gift card programs, and pull 100+ customizable reports—backed by 24/7 U.S.-based support.
Core product modules include:
- Point of Sale (iPad POS, advanced modifiers, half-and-half, customized floor plans)
- Front-of-House (QR code ordering, tableside ordering, self-ordering kiosks, customer-facing displays)
- Back-of-House (Manager's app, Advanced Reporting, kitchen touchscreen displays, inventory tracking, tip pooling)
- Rezku Online (white-label online ordering and delivery dispatch)
- Rezku Loyalty, Gift Cards, and Timecards (native loyalty, stored value, and labor)
Common data entities:
- Orders, Checks, Tickets, Line Items, Modifiers
- Menu Items, Categories, Modifier Groups, Price Levels
- Payments, Tips, Discounts, Gift Cards, Loyalty Balances
- Inventory Items, Counts, Recipes, Vendors
- Employees, Timecards, Shifts, Tip Pools
- Customers, Reservations, Reports
The Rezku Integration Challenge
Restaurants run their entire day on Rezku, but getting that operational data out programmatically is hard—Rezku is a system of record for sales and labor with no documented public developer API:
- No public API or developer portal: Rezku publishes no developer documentation, API keys, or self-serve access—integrations are negotiated partner-by-partner, leaving operators without a way to reach their own sales, check, and labor data
- iPad-first, cloud back office: Live ordering happens on iPad terminals while reporting lives in a web back office, so data is split across device-bound POS state and a separate cloud console
- Partner-gated connectors: Existing links to QuickBooks, Restaurant365, 7Shifts, Chowly, DoorDash, Grubhub, and Uber Eats are pre-built partner integrations, not an open surface you can build new automation against
- Multi-location fragmentation: Centralized reporting spans many venues, but each location's menus, price levels, and floor plans differ, so a generic scraper breaks across sites
- Report-only exports: Operators are limited to canned reports and CSV downloads, with no event-level feed of orders, payments, or voids for real-time pipelines
- Session and authentication friction: Back-office logins, session timeouts, and per-user permissions complicate any headless, always-on automation against the console
How Supergood Creates Rezku APIs
Supergood reverse-engineers Rezku's authenticated back-office flows and POS surfaces to deliver a resilient, normalized API layer for your Rezku account—so you can read and write your own restaurant data without waiting on a partner agreement.
- Handles back-office login, MFA, and per-user permissions securely in a managed session
- Maintains session continuity with automatic refresh and change detection across console updates
- Normalizes orders, payments, menu, inventory, and labor into consistent JSON objects across all your locations
- Aligns with each venue's menus, price levels, and modifier groups so multi-location data stays consistent
Use Rezku with AI agents: Rezku MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Rezku modules, locations, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Rezku adapter tailored to your account configuration and venue setup.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Rezku evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Rezku account using back-office credentials and MFA, returning a session token for downstream calls.
Orders
/ordersList orders and checks across locations with filters for date range, status, employee, and order type.
Orders
/create_orderCreate or push an order with line items, modifiers, and customer details against a venue's configured menu.
Menu
/menu_itemsRetrieve menu items, categories, modifier groups, and price levels for one or more locations.
Payments
/paymentsPull payments, tips, discounts, and gift card activity tied to checks for reconciliation and reporting.
Inventory
/inventoryRead inventory items, counts, recipes, and vendor records to sync stock and cost data downstream.
Use Cases
Sync sales and check data into your warehouse
- Pull orders, checks, line items, and modifiers across all locations into a single warehouse - Stream payment, tip, discount, and void events to BI and accounting tools - Reconcile gift card and loyalty balances against POS activity
Automate menu and price management
- Read menu items, categories, and modifier groups for each venue - Push menu, price level, and availability changes across multiple locations at once - Keep online ordering and third-party delivery menus aligned with the POS
Centralize labor and inventory reporting
- Pull timecards, shifts, and tip pools for payroll and labor cost analysis - Sync inventory counts, recipes, and vendor data into purchasing tools - Surface real-time sales-vs-labor metrics across venues without manual report exports
Feed AI agents and operational dashboards
- Expose normalized Rezku data to AI agents and copilots for natural-language reporting - Trigger alerts on voids, comps, and anomalous discounts in near real time - Power custom multi-location dashboards beyond the canned report set
Technical Specifications
Authentication
Back-office credentials and MFA (SMS, email, TOTP) handled in a managed session
Connectivity
Authenticated back-office and POS flows; no public Rezku developer API required
Response format
Normalized JSON across Orders, Menu, Payments, Inventory, and Labor objects
Rate limits
Adaptive throttling tuned to your account to avoid Rezku-side limits
Session management
Automatic session refresh, timeout recovery, and credential rotation
Data freshness
Near real-time pulls for orders and payments with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new orders, payments, voids, and menu changes
Latency
Sub-second reads on cached entities; multi-second writes when posting orders and menu updates
Throughput
Horizontally scaled workers sized to multi-location order and payment volume
Reliability
Retry, backoff, and idempotency keys for order, payment, and menu writes
Adaptation
Continuous monitoring of Rezku console and POS releases and per-venue configuration drift
Frequently asked questions
Rezku does not publish a documented public developer API or self-serve developer portal; existing connectors are pre-built partner integrations. Supergood provides an unofficial, normalized API against your authenticated Rezku account so you can reach your own order, payment, menu, and labor data.
Yes. Supergood profiles each venue's menus, price levels, modifier groups, and floor plans, then normalizes orders, payments, and labor across all your locations into a consistent schema.
Yes. Supergood operates against your authenticated Rezku surfaces independently of partner connectors like QuickBooks, Restaurant365, 7Shifts, or Chowly, so it complements rather than replaces them.
Yes. Beyond reads, the API supports writes such as creating orders and pushing menu, price level, and availability changes, with retries and idempotency keys to keep operations safe.
Supergood handles back-office login, MFA, session timeouts, and per-user permissions inside a managed, encrypted session, so your automation stays connected without manual re-login.