canonical: https://jentic.com/apis/lightspeed.app/lightspeed

# Lightspeed App Lightspeed Restaurant K-Series API

Jentic publishes the only available OpenAPI specification for Lightspeed Restaurant K-Series API, keeping it validated and agent-ready. The K-Series API gives restaurants programmatic access to menus, items, dine-in and takeout orders, staff, financials, and webhooks across multi-business operations. Twenty-two endpoints cover business listing, menu loading, order creation, rich item CRUD, shift and POS staff management, financial and sales reporting, and receipt retrieval. Authentication uses HTTP bearer tokens and supports both trial and production base URLs.

## For AI agents

Manage restaurant menus, dine-in and takeout orders, staff shifts, and sales reporting in Lightspeed K-Series via 22 bearer-authenticated endpoints.

## Scope

Does not handle retail e-commerce, payment-processor onboarding, or hardware fulfillment - use for Lightspeed Restaurant K-Series order, menu, and staff operations only.

## Capabilities

- Create dine-in and takeout orders against a Lightspeed Restaurant K-Series business
- List menus and load full menu definitions including categories and modifier groups
- Create, update, and delete rich items by SKU for menu engineering
- List shifts, manage POS staff, and retrieve receipts by reference
- Pull sales, financial, tax-rate, and payment-method data for accounting reconciliation
- Manage webhook subscriptions for order, payment, and staff event notifications

## Use cases

### Online Ordering Integration

Connect a third-party ordering channel to Lightspeed K-Series by creating dine-in or takeout orders through the API. POST `/o/op/1/order/local` and POST `/o/op/1/order/to-go` accept order line items with rich-item SKUs and modifiers. Replaces manual order entry for delivery aggregators and direct online ordering apps.

Example prompt: Create a takeout order against business ID 'biz-77' with items 'sku-burger' and 'sku-fries' and customer phone '+15551234567'

### Menu Engineering and Sync

Keep menus and rich items in sync between a central menu-management system and individual restaurant locations. The /rich-items endpoints expose full CRUD by SKU, and `/o/op/1/menu/load/{menuId}` returns the live menu structure. Enables central marketing teams to push changes to dozens of locations in a single workflow.

Example prompt: Create rich item with SKU 'sku-special-2026' priced at $14.99 and add it to menu ID 'menu-spring'

### Sales and Financial Reporting

Pull sales, tax-rate, and financial data nightly into a data warehouse for restaurant analytics. The /sales, /financials, /tax-rates, and /payment-methods endpoints expose reporting-grade data per business. Replaces CSV exports with structured pulls into BI tools.

Example prompt: Pull yesterday's sales for business ID 'biz-77' and post a daily summary with gross sales by payment method

### AI Agent Restaurant Assistant

An AI agent uses Jentic to discover Lightspeed K-Series operations by intent and creates orders, queries menus, and pulls receipts on a manager's behalf. Webhook subscriptions let the agent react to new orders. Credentials are isolated through Jentic so the bearer token never enters agent context.

Example prompt: Search Jentic for 'create a Lightspeed takeout order', load the operation schema, and execute it with the customer's order details

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/o/op/1/order/local` | Create a dine-in order |
| POST | `/o/op/1/order/to-go` | Create a takeout order |
| GET | `/o/op/1/menu/load/{menuId}` | Load a full menu by ID |
| PUT | `/rich-items` | Create or update a rich menu item |
| GET | `/sales` | Get sales data for a business |
| POST | `/webhooks` | Create a webhook subscription |

## Key resources

- **Order and Pay** — Create dine-in and takeout orders, list businesses, and load menus
- **Rich Items** — CRUD on menu items by SKU including pricing and modifiers
- **Staff** — Manage POS staff and list shifts
- **Financial** — Sales, financial, tax-rate, and payment-method reporting
- **Webhooks** — Subscribe to order, payment, and staff event notifications

## Why Jentic

- **Setup:** Wiring the Lightspeed Restaurant K-Series API by hand means setting its bearer token, choosing the trial or production lsk.lightspeed.app host, and learning which endpoints cover orders, menus, sales, and staff yourself. Through Jentic you install once, import the Lightspeed K-Series API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Lightspeed creates orders and updates items through operation endpoints like `/o/op/1/order/local` and /rich-items rather than pinning to a resource id in the path, so scope the agent to the operations it needs, such as creating a takeout order or reading sales. You leave out item or webhook writes unless you add them, so it only calls the ones you allow.
- **Credential handling:** Your Lightspeed bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a Lightspeed takeout order' or 'load a menu', and Jentic returns the matching K-Series operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Square API** — Restaurant and retail POS with built-in payments and online ordering
- **Toast POS API** — Restaurant-focused POS with deep menu and labor APIs
- **Shopify Admin API** — Surface Lightspeed restaurant items on a Shopify storefront for online ordering

## FAQ

### Why is there no official OpenAPI spec for Lightspeed Restaurant K-Series API?

Lightspeed does not publish a maintained OpenAPI specification for the Restaurant K-Series API. Jentic generates and maintains this spec so that AI agents and developers can call the K-Series API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Lightspeed Restaurant K-Series API use?

It uses HTTP bearer authentication. Tokens are issued by Lightspeed for each business and passed in the Authorization header. Through Jentic, bearer tokens are stored in your Jentic One instance and injected per request.

### Can I create both dine-in and takeout orders with this API?

Yes. POST `/o/op/1/order/local` creates dine-in orders and POST `/o/op/1/order/to-go` creates takeout orders. Both accept line items with rich-item SKUs and modifiers.

### What are the rate limits for the Lightspeed K-Series API?

The spec does not document explicit rate limits. Treat the API as moderately throttled per business token; respect HTTP 429 responses with a Retry-After header and prefer webhook subscriptions over polling for order updates.

### How do I subscribe to new-order webhooks through Jentic?

Run pip install jentic, then search Jentic with 'subscribe to Lightspeed webhooks' to retrieve POST /webhooks. Execute it with your callback URL and event types; Jentic handles the bearer token automatically.

### Is the Lightspeed Restaurant K-Series API free?

API access is included with paid Lightspeed Restaurant K-Series subscriptions. There is no free tier; pricing depends on the venue plan.

### Can I limit what my agent is allowed to do with the Lightspeed Restaurant K-Series API?

Yes. Because you run Jentic One yourself, your own rules decide which K-Series operations and credentials the agent may use. The K-Series API works through operation endpoints such as POST `/o/op/1/order/local`, POST `/o/op/1/order/to-go`, and /rich-items rather than fixed resource IDs, so you scope the agent to just the operations it needs, like creating a takeout order or reading /sales. Item writes and webhook subscriptions stay off unless you add them, so the agent calls only the endpoints you allow.