POSitouch API
POSitouch is a hospitality point-of-sale platform—now part of Shift4—used by fine dining, table service, quick service, fast casual, and bar/nightclub operators to run dining-room management, ordering, kitchen display, inventory, labor, and loyalty. An unofficial API lets you programmatically pull tickets, sales, menu items, employees, inventory, and reporting data—and push updates like orders, menu changes, and time entries back into POSitouch.
What is POSitouch?
POSitouch is a hospitality point-of-sale platform—now owned by Shift4—built for fine dining, table service, quick service, fast casual, and bar or nightclub operations. Restaurants use POSitouch to manage dining-room layouts and table status, ring and route orders, run kitchen display systems, control inventory and food cost, manage labor, and drive gift, loyalty, online ordering, and reservation workflows, with reporting surfaced through Shift4's Lighthouse business-management system.
Core product areas include:
- Dining Room Management (table layouts, real-time status, check splitting, course firing)
- Kitchen Display System (KDS) with station routing and paper reduction
- Inventory Control (food cost, suppliers, purchase orders, receiving, transfers)
- Time Stamp / Labor Module for workforce cost control
- Online Ordering / Delivery (SkyTab Online, DoorDash, Olo, Menufy)
- Gift, Loyalty, and Reservation management (eReserve, EatApp, online booking)
- Reporting and Credit Card Authorization through Shift4's Lighthouse and payment processing
Common data entities:
- Tickets/Checks, Orders, Line Items, Modifiers, Voids
- Menu Items, Categories, Price Tiers, Modifier Groups
- Tables, Sections, Reservations, Wait Lists
- Payments, Tenders, Gift Cards, Loyalty Accounts
- Employees, Time Entries, Job Codes, Labor Shifts
- Inventory Items, Suppliers, Purchase Orders, Sales Reports
The POSitouch Integration Challenge
Restaurants run high-volume operations on POSitouch every shift, but turning an on-premise, terminal-based POS into API-driven automation is non-trivial:
- On-premise, Windows-based architecture: POSitouch runs on local terminals and back-office servers, so data lives on-site rather than behind a uniform cloud API
- Legacy platform status: Shift4 directs new customers to SkyTab, so POSitouch lacks an actively published public developer API
- Marketplace and partner gates: Many integrations flow through the Shift4 Marketplace and require partner agreements before data access
- Per-location configuration: Menus, modifiers, price tiers, and table layouts are tailored per restaurant—generic integrations break across sites
- Reporting locked in Lighthouse: Sales, labor, and inventory analytics surface through Shift4's Lighthouse portal rather than a programmatic feed
- Real-time order flow: KDS routing, course firing, and online-ordering hand-offs demand low-latency, ordered event handling
How Supergood Creates POSitouch APIs
Supergood reverse-engineers POSitouch's authenticated back-office and Lighthouse portal flows to deliver a resilient, normalized API layer for your locations—without waiting on a public developer program.
- Handles username/password and MFA securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes tickets, menu, payments, labor, and inventory so you integrate once across locations
- Aligns with per-location menu, modifier, and table configuration to keep data consistent across sites
Use POSitouch with AI agents: POSitouch MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your locations, modules, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready POSitouch adapter tailored to your menu and location configuration.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as POSitouch and Shift4 evolve.
API Endpoints
Authentication
/authenticateAuthenticate to a POSitouch location's back-office using username/password or MFA and obtain a session token for downstream calls.
Orders
/ticketsList tickets and checks with filters for location, date range, server, status, and tender type.
Orders
/create_orderSubmit a new order with line items, modifiers, and routing so it fires to the appropriate KDS station.
Menu
/menu_itemsRetrieve menu items, categories, price tiers, and modifier groups for a location's current configuration.
Labor
/time_entriesPull employee time entries, job codes, and labor shifts for payroll and scheduling systems.
Reporting
/sales_reportsRetrieve sales, payment, and inventory reporting data surfaced through Lighthouse for a location and period.
Use Cases
Sync sales and ticket data into your warehouse
- Pull closed tickets, line items, modifiers, and voids across all locations into a single warehouse - Stream payment, tender, and gift/loyalty events to downstream BI and finance tools - Reconcile daily sales totals against Lighthouse reporting without manual exports
Automate menu and price management
- Push menu item, category, and price-tier changes into POSitouch across sites - Keep modifier groups and 86'd items in sync with online-ordering channels - Roll out time-based pricing and promotions from a central menu system
Feed labor and time data to payroll
- Pull employee time entries, job codes, and shifts for payroll processing - Reconcile labor cost against sales for real-time labor-percentage tracking - Surface overtime and clock anomalies to managers without portal logins
Connect inventory and food-cost systems
- Sync inventory items, suppliers, and purchase orders with back-office tools - Match item-level sales to depletion for accurate food-cost contribution - Trigger reorder workflows when on-hand counts fall below par
Technical Specifications
Authentication
Username/password and MFA handled in a managed session
Connectivity
Authenticated POSitouch back-office and Shift4 Lighthouse portal flows, surfaced as a normalized API
Response format
Normalized JSON across tickets, menu, payments, labor, and inventory objects
Rate limits
Adaptive throttling tuned per location to avoid back-office and Lighthouse limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for tickets 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 ticket close, payment, menu change, and clock-in/out events
Latency
Sub-second reads on cached entities; multi-second writes when posting orders and menu updates
Throughput
Horizontally scaled workers sized to multi-location, high-volume service periods
Reliability
Retry, backoff, and idempotency keys for orders, payments, and menu writes
Adaptation
Continuous monitoring of POSitouch, Lighthouse, and Shift4 Marketplace changes and per-location configuration drift
Frequently asked questions
POSitouch is a legacy POS now owned by Shift4, which directs new customers to SkyTab, so it lacks an actively published public developer API. Supergood works against your authenticated POSitouch back-office and Lighthouse sessions to deliver a normalized API without a partner program.
Yes. Supergood profiles each location's menu, modifier, price-tier, and table configuration and normalizes responses so you integrate once across all sites rather than building per-location connectors.
No. Supergood operates against your existing POSitouch and Lighthouse credentials and authenticated sessions. Marketplace partner agreements are only relevant when you specifically want to consume a third-party service brokered through Shift4.
You can read tickets, menu items, payments, labor/time entries, inventory, and reporting data, and write updates like new orders, menu and price changes, and time entries back into POSitouch.
POSitouch runs on local Windows terminals and back-office servers. Supergood connects through authenticated back-office and Lighthouse flows, tuning network configuration to your environment so on-site data is exposed as a consistent cloud API.