Integration · Lightspeed
Lightspeed Restaurant integration for multi-location groups
Connect Lightspeed Restaurant (K-Series) to your ordering app, master menu and franchise reports. Which access route you get decides what you can build, so we start there.
Takes two minutes. An engineer reads it, and Max replies within 1 business day.
- API
- REST, OAuth 2, webhooks for partners
- Access
- Partner program or paid merchant add-on
- Versions
- In the path, changelog
- Markets
- US, CA, UK, CH, DE
In short
A Lightspeed integration connects Lightspeed Restaurant (K-Series) to other systems through its REST APIs: items, orders and payments, financial reports, staff and reservations. Access is limited: partners get webhooks and order injection, while a merchant's custom integration is a paid add-on without webhooks or order scopes. Auth is OAuth 2 with 25-minute tokens. dev.family builds Lightspeed connectors for multi-location groups and keeps them running under an SLA.
What data moves
What a Lightspeed Restaurant integration moves
Read means we can get it from Lightspeed. Write means we can send it to Lightspeed.
| Object | Read | Write | What the API supports |
|---|---|---|---|
| Items and menus | Yes | Yes | Items API creates and updates items; Rich Item for full detail |
| Orders | Yes | Partly | Order injection through Order and Pay needs the partner orders scope |
| Sales and payments | Yes | No | Financial API, read-only reporting with cursor pagination |
| Staff and shifts | Yes | Partly | Staff API for users and shifts |
| Reservations and floor plans | Yes | Partly | Reservations scope is partner-only |
| Guests and loyalty | No | No | No guest or loyalty API found in the docs |
Common setups
How groups connect Lightspeed
Reports across POS
Financial API data from Lightspeed sits next to another POS in one warehouse.
Delivery into Lightspeed
Delivery orders reach Lightspeed through middleware with partner access.
One menu for every brand
Items and prices go out to each POS from one source.
API access
How Lightspeed API access works
Lightspeed limits API access to partners and approved merchants. A software company applies to the partner program and gets the developer portal, webhooks and order scopes. A restaurant group can buy API access as a paid add-on through its Lightspeed account manager; Lightspeed provisions it within 48 hours, one client per business account.
Every connection uses OAuth 2 with the merchant's consent. Access tokens last 25 minutes and refresh tokens are single-use, so the connector has to rotate them reliably.
Docs api-docs.lsk.lightspeed.app · changelog at api-docs.lsk.lightspeed.app/changes · checked November 9, 2026
What we need from you
- Your Lightspeed account and business locations
- Which route you have: partner app or custom add-on
- What you need: reports, menus or orders
- A trial or test location
Getting access:
custom API access within 48 hours after your account manager approves it; the partner route takes longer.
Platform limits
Where Lightspeed integrations break
Custom access can't take orders. A merchant's custom integration has no webhooks and no orders or reservations scopes. If you need order injection, plan for the partner route or middleware.
Short-lived tokens. Access tokens expire after 25 minutes and refresh tokens work once. A failed refresh means a merchant has to reconnect.
Three pagination styles. Items, Rich Item, Staff and Financial paginate in different ways. Every sync job needs its own paging logic.
No published rate limits. Lightspeed doesn't publish request limits, so bulk syncs need backoff.
Breaking changes in new versions. Breaking changes ship as a new version in the path; the changelog marks them, without a stated notice period.
Run
Who fixes it when the platform changes its API
Monitoring
We check the connector against the live API every day and log every failed call.
Versions
We track the platform's changelog and move the connector to a new version before the old one is retired.
Alerts
Lost or stuck orders page the on-call engineer, who fixes them under the SLA.
Questions
Didn't find your answer? Ask on the call.
Lightspeed publishes its K-Series API reference at api-docs.lsk.lightspeed.app, but access is limited to approved partners and merchants. Developers apply to the partner program; a merchant can buy API access for a custom integration through its account manager.
A partner integration can inject orders and use webhooks. A custom integration, bought by the merchant as a paid add-on, has no webhooks and no orders or reservations scopes, so it suits reporting and menu work rather than ordering. Lightspeed doesn't build or maintain custom integrations.
Items and menus, orders and payments through Order and Pay (partners only), sales and payments through the Financial API, staff shifts, reservations, floor plans and tax previews.
This page covers Lightspeed Restaurant, the K-Series. Lightspeed Retail is a different product with a different API, often searched together with Shopify and ecommerce integrations.
Provisioning custom API access takes up to 48 hours, according to Lightspeed. The build depends on the route: reporting through the Financial API is smaller than order injection through the partner program. We fix the price per scope before we start.
Lightspeed launched its restaurant product in the US, Canada, the UK, Switzerland and Germany. The API is the same; check that your plan includes API access in each market.
Get a scope estimate for your Lightspeed integration
Tell us which Lightspeed locations you run, what access you have and what data you need. An engineer will reply with the right route and how long it takes.
a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work
Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors
Max will reply within 1 business day with what's possible, what access we need and a rough timeline.