Lunchbox API
Lunchbox is an enterprise restaurant technology platform unifying web and app ordering, B2B catering, order aggregation, marketing CRM, loyalty, and payments across multi-location operations. Its Open API lets you programmatically retrieve locations, menus, and guest accounts, place orders directly into the POS, and receive delivery and order events via webhooks—so you can pull order, menu, and guest data and push new orders and menu updates back into Lunchbox.
What is Lunchbox?
Lunchbox is an enterprise restaurant technology platform that enables B2B catering, multi-channel ordering, and guest engagement for multi-location operations on a single platform. Restaurants use Lunchbox to run branded web and app ordering, manage catering, aggregate menus across locations, drive marketing and loyalty campaigns, handle payment disputes, and connect their wider tech stack through an Open API that links to 100+ technology partners.
Core product modules include:
- Web & App Ordering (branded customer ordering experiences)
- Catering (dedicated B2B catering order management)
- Order Aggregation (automated, POS-integrated menu management across 50+ locations and third-party channels)
- Marketing CRM (email, SMS, and push notification campaigns)
- Loyalty & Scan to Pay (customer loyalty programs)
- Dispute Manager (automation for third-party payment disputes)
- Open API (custom integrations with 100+ technology partners, including OPEN Payments)
Common data entities:
- Locations, Menus, Menu Items, Modifiers
- Orders, Checks, Payments, Disputes
- Guest Accounts, Loyalty Profiles, Marketing Audiences
- Catering Orders, Delivery Events
The Lunchbox Integration Challenge
Enterprise restaurant brands run high-volume ordering and catering on Lunchbox daily, but turning its multi-channel, POS-integrated workflows into reliable API-driven automation is non-trivial:
- Split API surface: Lunchbox 2.0 OPEN APIs are organized into a Core API for ordering and frontend interfaces and a Management API for administrative functions—coverage and availability differ by capability
- Multi-location menu sprawl: Order aggregation spans 50+ locations and third-party marketplaces, each with its own menu state and POS mapping
- POS-coupled order flow: Orders place directly into the underlying POS, so integrations must respect POS-side menu, modifier, and availability rules
- Partner-gated access: API access and the 100+ technology-partner ecosystem run through reseller and referral programs, requiring partnership or account provisioning before keys are issued
- Webhook-driven delivery: Last-mile delivery and order events rely on custom webhooks that must be configured, validated, and monitored per brand
- Payments and disputes: OPEN Payments processing and Dispute Manager add transaction and chargeback workflows that need careful reconciliation
How Supergood Creates Lunchbox APIs
Supergood reverse-engineers authenticated Lunchbox sessions, the Core and Management Open APIs, and dashboard flows to deliver a resilient, normalized API layer for your Lunchbox account—across ordering, catering, menus, guests, and payments.
- Handles credential-based login and MFA securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Locations, Menus, Orders, Guests, and Payments so you integrate once and rely on consistent objects
- Maps menus and orders to the right POS-integrated location and respects per-location availability rules
Use Lunchbox with AI agents: Lunchbox MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, locations, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Lunchbox adapter tailored to your account, locations, and POS configuration.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Lunchbox evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Lunchbox account and obtain a session token for downstream Core and Management API calls.
Locations
/locationsRetrieve restaurant locations with operating status, address, and POS-integration details across the brand.
Menus
/menusPull menus, menu items, and modifiers for a location in read-only form for ordering or digital menu boards.
Menus
/menusUpdate menu items, availability, and modifiers through the Management API and sync changes to the POS.
Orders
/ordersFetch orders and checks with status, channel, and payment details, including catering and aggregated channels.
Orders
/create_orderPlace an order directly into the location's POS with items, modifiers, guest, and fulfillment details.
Guests
/guestsRetrieve guest accounts and loyalty profiles for CRM, marketing, and personalization workflows.
Use Cases
Sync orders and menus across locations
- Pull orders, checks, and payments from web, app, catering, and aggregated channels into a single warehouse - Retrieve menus, items, and modifiers per location for analytics and digital menu boards - Push menu and availability updates back through the Management API to keep POS menus current
Automate order placement into the POS
- Place orders directly into the location's POS with items, modifiers, and fulfillment details - Route last-mile delivery and order status via custom webhooks to delivery and ops tools - Reconcile OPEN Payments transactions and Dispute Manager chargebacks against orders
Unify guest, loyalty, and marketing data
- Sync guest accounts and loyalty profiles into CRM and customer-data platforms - Build marketing audiences for email, SMS, and push campaigns from order behavior - Surface loyalty and Scan to Pay activity to downstream personalization tools
Power B2B catering operations
- Pull catering orders and delivery events into ERP and accounting systems - Trigger fulfillment and routing workflows when catering orders are placed or updated - Report catering revenue and ROI alongside on-premise and digital channels
Technical Specifications
Authentication
Credential-based login and MFA handled in a managed session, layered over Lunchbox Open API access keys
Connectivity
Authenticated sessions plus the Lunchbox 2.0 Core and Management Open APIs where exposed by your account
Response format
Normalized JSON across Locations, Menus, Orders, Guests, and Payments objects
Rate limits
Adaptive throttling tuned to your account to avoid Lunchbox-side and POS-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for orders, menus, and guests with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Custom webhook support for order placement, status changes, and last-mile delivery events
Latency
Sub-second reads on cached entities; multi-second writes when posting orders into the POS
Throughput
Horizontally scaled workers sized to enterprise multi-location ordering volume
Reliability
Retry, backoff, and idempotency keys for order placement and menu updates
Adaptation
Continuous monitoring of Lunchbox releases, POS integrations, and partner-ecosystem changes
Frequently asked questions
Yes. Supergood works across the Lunchbox 2.0 Core API for ordering and frontend interfaces and the Management API for administrative functions like creating menus, fetching orders, and updating locations, exposing both through one normalized surface.
Yes. Lunchbox places orders directly into the underlying POS, and Supergood respects per-location menu, modifier, and availability rules so orders post correctly across all your locations.
Supergood works with your existing Lunchbox account and entitlements. Where Lunchbox gates Open API access through its reseller or referral programs, we operate against your provisioned account rather than requiring a separate generic integration.
Yes. B2B catering orders and orders aggregated from third-party marketplaces are normalized alongside native web and app orders, so you get a consistent view across every channel.
OPEN Payments transactions and Dispute Manager chargebacks are exposed through the normalized API surface, so you can reconcile payments and disputes against the orders that generated them.