Introduction
This document describes the target OpenApp architecture and business operations for restaurant POS integrations.
Architecture
Each physical restaurant location should have its own OpenApp integration profile. Product listings, menu data, prices, availability, POS credentials, queue configuration, callbacks, health, and status are scoped to that location profile.
Authorization
POS-to-OpenApp HTTP calls use OpenApp Merchant API HMAC authentication. This applies to POS callbacks, POS-pushed events, health reporting, and other POS-initiated HTTP calls after activation.
Queue Communication
Queue delivery is intended for POS systems that cannot receive inbound OpenApp HTTP calls.
Data Models
This page is the reference for all POS integration message payloads, shared base models, and enums.
Integration Flows
7 items