← Back to all docs

Qu POS API

Qu is an API-first restaurant commerce platform that unifies POS, kiosk, drive-thru, online ordering, kitchen display, menu management, and reporting for enterprise QSR and fast-casual brands. An unofficial API lets you programmatically pull orders, menus, store and channel data, loyalty, and payment records—and push updates like new orders, menu changes, and channel configuration back into Qu.

By Alex Klarfeld•May 30, 2026
Qu POS API

What is Qu POS?

Qu is an API-first restaurant commerce platform built for enterprise quick-service and fast-casual brands, positioning itself as an evolution beyond traditional point-of-sale. Restaurants use Qu to run omnichannel ordering across POS terminals, kiosks, drive-thru, and online; orchestrate the kitchen with a Kitchen Display System; manage unified menus across channels; administer brand, channel, and franchise operations; and surface unified data and reporting—built on a containerized, REST-API-centered architecture.

Core product areas include:

  • Omnichannel Ordering (POS terminals, kiosk, drive-thru, online ordering, third-party ordering)
  • Kitchen Orchestration (Kitchen Display System, order status tracking, equipment intelligence)
  • Enterprise Management (unified menu management, channel management, brand and franchise management)
  • Unified Data and Reporting plus a mobile insights platform
  • Partner Ecosystem (certified integrations across accounting, loyalty, delivery, payments, and labor)

Common data entities:

  • Orders, Order Items, Modifiers, Channels, Order Status
  • Menus, Categories, Items, Prices, Availability
  • Stores, Locations, Brands, Franchises, Terminals
  • Payments, Tenders, Checks, Discounts, Tax
  • Loyalty Members, Offers, Rewards, Transactions
  • Sales, Labor, and Inventory reporting outputs

The Qu POS Integration Challenge

Qu is explicitly API-first, but turning enterprise restaurant operations into reliable, account-specific automation is still non-trivial:

  • Partner certification gate: Qu runs a formal partner program and certification process, so production API access typically requires an approved integration agreement before keys are issued
  • Versioned Data Access API: Calls are prefixed with api/v3 and scoped to specific resources—coverage and behavior vary by version and the operator's deployment
  • Pull-based order flow: Third-party orders are posted to the Data Access API and then pulled by in-store POS systems, so timing, retries, and acknowledgements must be handled carefully
  • Multi-brand, multi-location modeling: Brand, franchise, store, and channel hierarchies each carry their own IDs and menu scoping, which generic integrations break across
  • Unified menu complexity: Menus, modifiers, pricing, and availability are managed centrally but vary per channel and location, complicating consistent reads and writes
  • Operational data spread: Sales, labor, and inventory reporting outputs live across modules and partner integrations rather than a single normalized endpoint

How Supergood Creates Qu POS APIs

Supergood reverse-engineers authenticated sessions and Qu's REST Data Access API to deliver a resilient, normalized API layer for your Qu account—across ordering, menus, stores, and reporting—without waiting on a custom certification project.

  • Handles credential and token-based authentication, including MFA, securely in a managed session
  • Maintains session continuity with automated refresh and change detection across api/v3 endpoints
  • Normalizes responses across orders, menus, stores, payments, and loyalty so you integrate once and rely on consistent objects
  • Aligns with brand, franchise, store, and channel hierarchies so reads and writes respect your account's scoping and entitlements

Use Qu POS with AI agents: Qu POS MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your modules, brands, channels, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a hardened Qu adapter tailored to your account configuration, channel hierarchy, and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Qu evolves.

qu

API Endpoints

Authentication

POST/authenticate

Authenticate to a Qu account using credentials or token-based auth and obtain a session for downstream api/v3 calls.

Ordering

GET/orders

List orders across POS, kiosk, drive-thru, online, and third-party channels with filters for store, channel, status, and date range.

Ordering

POST/create_order

Post a new third-party or online order into the Data Access API for in-store POS systems to pull and fulfill.

Menus

GET/menus

Retrieve unified menus, categories, items, modifiers, pricing, and availability scoped by brand, store, and channel.

Locations

GET/stores

List stores, locations, brands, and franchises with terminal and channel configuration.

Reporting

GET/sales_reports

Pull sales, payment, and check-level reporting outputs for reconciliation and analytics.

Use Cases

Sync orders across every channel into one warehouse

- Pull POS, kiosk, drive-thru, online, and third-party orders into a single normalized dataset - Stream order, item, and status events to downstream BI, analytics, and reconciliation tools - Match checks, tenders, and discounts across channels for unified sales reporting

Push third-party and online orders into stores

- Post new online and marketplace orders into the Data Access API for in-store POS pull - Handle acknowledgements, retries, and status updates so orders land reliably - Route order changes and cancellations back to the originating channel

Keep menus and pricing consistent across brands

- Read unified menus, modifiers, and availability scoped by brand, store, and channel - Push menu, price, and availability changes from a central catalog into Qu - Detect channel-specific overrides and reconcile them against the master menu

Centralize multi-location sales and operations data

- Pull store, brand, and franchise hierarchies with terminal and channel configuration - Aggregate sales, labor, and inventory reporting outputs across locations - Surface delinquent, anomalous, or high-variance stores to operations workflows

Technical Specifications

Authentication

Credential and token-based auth, including MFA, handled in a managed session

Connectivity

Authenticated sessions plus Qu's REST Data Access API, with calls prefixed api/v3

Response format

Normalized JSON across Orders, Menus, Stores, Payments, and Loyalty objects

Rate limits

Adaptive throttling tuned to your account to avoid Qu-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for orders and menus 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, order status changes, menu updates, and payment events

Latency

Sub-second reads on cached entities; multi-second writes when posting orders and menu changes

Throughput

Horizontally scaled workers sized to high-volume QSR and multi-brand order traffic

Reliability

Retry, backoff, and idempotency keys for order posting and menu updates

Adaptation

Continuous monitoring of Qu releases, api/v3 changes, and account-specific configuration drift

Frequently asked questions

No. Supergood works with your existing Qu account and authenticated sessions. The formal partner certification process is only required when you want to ship a generally available certified integration through Qu's partner program.

Yes. Supergood normalizes orders across POS terminals, kiosk, drive-thru, online ordering, and third-party channels, so you integrate order, item, and status data once across the whole omnichannel surface.

Each account is profiled against its brand, franchise, store, channel, and terminal hierarchy. Supergood preserves these IDs and scoping rather than forcing a flat, generic schema.

Yes. Beyond reads, the API supports posting third-party and online orders into the Data Access API and pushing menu, pricing, and availability changes, with retries and acknowledgements handled for you.

Supergood tracks Qu's api/v3 Data Access API and adapts as resources and behavior change across versions, so your integration keeps working without manual rework when Qu updates the platform.

Related APIs in POS / Hospitality

POS / Hospitality

Retail Pro API

Retail Pro is a specialty-retail POS and retail management platform built on the modular Retail Pro Prism server, deployed per-customer with its own REST API framework. An unofficial API lets you programmatically pull transactions, inventory, customers, employees, and store data—and push updates like sales receipts, item changes, price adjustments, and customer records—across each Prism deployment without partner-license gating or per-server credentials slowing you down.

POS / Hospitality

Revel Systems API

Programmatically access Revel Systems POS data—orders, menu items, inventory, and customer loyalty—with a stable REST API. Supergood builds and operates production-grade, unofficial Revel integrations so your team can automate front-of-house and back-office processes without heavy custom engineering

POS / Hospitality

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.

POS / Hospitality

Shopify POS API

Shopify POS is the in‑store point‑of‑sale experience that connects to your Shopify store, letting retailers sell in person while syncing inventory, customers, orders, discounts, and payments across locations. An unofficial API lets you programmatically pull POS orders with tender brea

POS / Hospitality

Slice API

Slice runs Slice Register, the point-of-sale and shop-management system that independent pizzerias use as their back-office system of record—the register where the shop rings up phone, online, and walk-in orders, manages one synced menu, processes payments, and watches sales and daily totals in real time. This unofficial API surfaces that back-office operating data—the pizzeria's own orders, menu/catalog, sales, payments, customers, and register reporting—not the consumer-facing Slice marketplace. Programmatically pull orders, menu items, sales and daily totals, payments and payouts, and customer records, and push menu and price updates back into the shop's register.

POS / Hospitality

Sling API

Sling is a cloud workforce management platform—now part of Toast—for employee scheduling, time tracking, team communication, task management, PTO, and labor-cost control across shift-based businesses. An unofficial API lets you programmatically pull shifts, timesheets, employees, groups, and locations, and push updates like new shifts, time-off approvals, and schedule changes back into Sling.

Ready to get a real API?