← Back to all docs

Lightspeed Restaurant API

Lightspeed Restaurant is a cloud point-of-sale platform for hospitality, powering ordering, payments, inventory, kitchen display, reservations, and analytics across more than 144,000 locations. An unofficial API lets you programmatically pull menus, orders, checks, payments, customers, inventory, and sales data—and push updates like new orders, menu changes, and reservations back into Lightspeed Restaurant.

By Alex KlarfeldMay 30, 2026
Lightspeed Restaurant API

What is Lightspeed Restaurant?

Lightspeed Restaurant is a cloud-based point-of-sale platform built for hospitality businesses, serving more than 144,000 locations globally including 200+ Michelin-starred restaurants. It combines a fast POS with online and tableside ordering, integrated payments, ingredient-level inventory, a Kitchen Display System, reservations, loyalty, and analytics so operators can run front-of-house and back-of-house from a single system across one or many locations.

Core product areas include:

  • Point of Sale with customizable menus, tableside handhelds, and a Customer Facing Display
  • Order Anywhere (online ordering, tableside ordering, QR-code ordering) and delivery order consolidation
  • Kitchen Display System (KDS) connecting front-of-house and back-of-house teams
  • Lightspeed Payments, accounting automation, payroll & workforce management, and Capital financing
  • Inventory Management down to the ingredient level, floor plan customization, and reservations
  • Advanced Insights, Benchmarks & Trends analytics, and loyalty program integration

Common data entities:

  • Menus, Menu Items, Modifiers, Allergens, SKUs
  • Orders, Checks, Payments, Receipts, Tax Breakdowns
  • Businesses, Business Locations, Revenue Centers, Accounting Groups
  • Customers, Loyalty records, Reservations
  • Staff, Users, Shifts, Permissions
  • Inventory items, Sales data, Tax rates, Payment methods

The Lightspeed Restaurant Integration Challenge

Restaurants run service-critical workloads on Lightspeed Restaurant every day, but turning POS and back-office workflows into reliable API-driven automation is non-trivial:

  • Multiple product series: Lightspeed Restaurant ships as K-Series, O-Series, L-Series, and the legacy U-Series (Upserve), each with its own API surface, object model, and endpoint coverage
  • Partner API gates: full programmatic access requires Partner API approval, so direct integrations are not available to every operator out of the box
  • Continuous change: the K-Series API is described as in continuous development and subject to change, so integrations drift as endpoints evolve
  • Mixed authentication: API keys, Basic Auth, Bearer tokens, and OAuth2 are used across surfaces and webhooks, complicating headless automation
  • Multi-location complexity: businesses, business locations, and revenue centers each carry their own IDs and entitlements that must be reconciled across a group
  • Real-time service constraints: orders, checks, and kitchen events move fast during service, so polling and reconciliation must stay current without overloading the POS

How Supergood Creates Lightspeed Restaurant APIs

Supergood reverse-engineers authenticated browser flows and Lightspeed Restaurant's published API surfaces to deliver a resilient, normalized API layer for your account—across the K-Series, O-Series, and legacy series your locations run.

  • Handles API key, Basic Auth, Bearer token, and OAuth2 flows securely in a managed session
  • Maintains session continuity with automated refresh and change detection as series APIs evolve
  • Normalizes responses across menus, orders, payments, inventory, and customers so you integrate once and rely on consistent objects
  • Reconciles businesses, business locations, and revenue centers so multi-location groups share a single object model

Use Lightspeed Restaurant with AI agents: Lightspeed Restaurant MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your Lightspeed Restaurant series, locations, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready Lightspeed Restaurant adapter tailored to your series, locations, and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Lightspeed Restaurant evolves.

lightspeed

API Endpoints

Authentication

POST/authenticate

Authenticate to a Lightspeed Restaurant account using API key, Bearer token, or OAuth2 and obtain a session for downstream calls.

Menus

GET/menus

List all POS menus, menu items, modifiers, and allergens for a business location.

Orders

GET/orders

Retrieve dine-in and takeout orders with checks, line items, and status filters.

Orders

POST/create_order

Create a new dine-in or takeout order against a menu and revenue center.

Payments

GET/payments

Pull payments, receipts, and tax breakdowns across orders and checks.

Operations

GET/business_locations

List businesses, business locations, and revenue centers with sales data and tax rates.

Use Cases

Sync menus and inventory to downstream systems

- Pull menus, items, modifiers, and allergens into a central catalog - Reconcile ingredient-level inventory across locations - Keep third-party ordering channels aligned with POS menu changes

Stream orders and payments to analytics

- Capture dine-in and takeout orders, checks, and line items in real time - Stream payments, receipts, and tax breakdowns to BI and accounting tools - Reconcile sales data across revenue centers for unified reporting

Automate online and tableside ordering

- Create orders against menus and revenue centers without manual entry - Push order status updates to the Kitchen Display System - Consolidate delivery and QR-code orders into one order pipeline

Keep multi-location operations in sync

- Pull business locations, staff, shifts, and permissions across a group - Surface benchmarks and trends for multi-site comparison - Sync customer and loyalty records across all locations

Technical Specifications

Authentication

API key, Basic Auth, Bearer token, and OAuth2 handled in a managed session

Connectivity

Authenticated browser flows plus Lightspeed Restaurant's REST API surfaces across K-Series, O-Series, and legacy series

Response format

Normalized JSON across menus, orders, payments, inventory, and customer objects

Rate limits

Adaptive throttling tuned to your account to avoid POS-side limits during service

Session management

Automatic session refresh, token rotation, and re-auth handling across series

Data freshness

Near real-time pulls for orders, checks, and payments with optional scheduled syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for orders, payments, reservations, and staff changes where exposed

Latency

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

Throughput

Horizontally scaled workers sized to multi-location order and payment volume

Reliability

Retry, backoff, and idempotency keys for order creation and payment posting

Adaptation

Continuous monitoring of Lightspeed Restaurant series releases and endpoint changes

Frequently asked questions

Supergood works across the K-Series, O-Series, and L-Series, as well as the legacy U-Series (Upserve). We profile which series your locations run and normalize the differing object models into a single API surface.

No. Supergood works with your existing Lightspeed Restaurant account and authenticated sessions, so you do not need to go through the Partner API gate to get programmatic access to your own data.

Yes. Businesses, business locations, and revenue centers are reconciled into one normalized model, so multi-location groups can pull menus, orders, payments, and staff data across every site consistently.

Yes. Orders, checks, and payments are pulled near real time with adaptive throttling, so you can stream service activity to analytics and accounting without overloading the POS.

Menus, items, modifiers, allergens, and ingredient-level inventory are exposed through the normalized API, and continuous monitoring keeps integrations aligned as the underlying series APIs change.

Ready to get a real API?