Reference · built on requestConnectorHospitality & property systems

Lightspeed Restaurant

Sales, checks, menus, items, staff shifts, and online orders from Lightspeed Restaurant K-Series locations.

Request accessPricing ↗

About

Lightspeed Restaurant K-Series is a restaurant point of sale. Its REST API at api.lsk.lightspeed.app is split into Financial, Online Ordering (Order and Pay), Items, Rich Item, Staff, Reservations for Platforms, PMS, ID Cards, and Tax Preview groups, each scoped by business location. Access is reserved for Lightspeed's approved integrators and approved merchants.

Through Fibric, an operator reads closed sales, open checks, and shift events, then proposes an order, a payment, or an item change for your approval. The change goes through once, never twice, and leaves a receipt with what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Lightspeed Restaurant and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Closed sales per business location through GET /f/v2/business-location/{businessLocationId}/sales, sorted by timeClosed, and business-day totals through sales-daily
  • Open checks through GET /o/op/1/order/table/getCheck and single checks by account identifier
  • Menus, modifiers, and discounts through /o/op/1/menu, plus item availability through /o/op/1/itemAvailability
  • Items through GET /items/v1/items and rich item data such as allergens, pictures, and locales through /i/richItem/{businessId}
  • Shifts and POS users through /staff/v1/businessLocations/{businessLocationId}, with shift.created, shift.updated, and shift.deleted webhooks
  • Order, payment, and account events through the Order and Pay webhook: CLOSED, CHECK_WAS_UPDATED, READY_FOR_PICKUP, CANCELLED, SUCCESS, FAILURE
  • Tax rates, payment methods, and accounting groups through the Financial API

Proposed actions

  • Target capability: propose a local or to-go order through POST /o/op/1/order/local or /o/op/1/order/toGo
  • Target capability: propose a payment on a check through POST /o/op/1/pay
  • Target capability: propose an item change through PUT /items/v1/items/{id} or a new item through POST /items/v1/items
  • Target capability: propose a printed message to the kitchen or bar through POST /o/op/1/printMsg
  • Target capability: propose a POS user record through POST or PUT on /staff/v1/businessLocations/{businessLocationId}/userTypes/POS

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Watch what sells out

    SALES_RESTRICTION_UPDATED events and /o/op/1/itemAvailability show which items are off. The operator proposes the online menu update and records when the item returns.

    With 86 Watch

  • Cover the shift

    shift.created and shift.updated webhooks plus the shift endpoint show who is on. When a shift falls short, the operator proposes an open shift offer.

    With Shift Coverage, Open Shift Offer

  • Forecast covers per location

    Closed sales carry covers per receipt. The operator builds a forecast per business location and proposes staffing and prep levels for your approval.

    With Cover Forecast

  • Tie sales to the bank

    Lightspeed Payments data and business-day sales give the daily totals. The operator matches them to deposits and proposes the entries to review.

    With Bank Reconciliation

Requirements

  • An API client from the Developer Portal, which is open to approved Lightspeed integrators; merchants ask their account manager for access
  • Scopes matched to the work: orders-api, financial-api, items, staff-api, propertymanagement, id-cards, or reservations-api
  • The Staff API needs the authorization code grant and the ROLE_CONFIG_USERS permission
  • An https redirect URI; client ids are bound to one environment, trial or production
Authentication
OAuth2 authorization code grant only, at https://auth.lsk-prod.app/realms/k-series/protocol/openid-connect (trial: auth.lsk-demo.app); access tokens last 25 minutes and refresh tokens 40 days with the offline_access scope.

Limits

  • Financial V2 pages hold at most 100 sales and use nextPageToken; V1 pages hold up to 1000 with HATEOAS links
  • V2 sales endpoints do not yet support historical dating of back-office transactions; V1 does
  • Refresh tokens without offline_access expire after 30 minutes
  • Item availability and online order readiness webhooks need business locations registered on the webhook first

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Lightspeed Restaurant ↗

Questions and answers

Which authentication does the K-Series API support?
Only the OAuth2 authorization code grant. No other method is supported. Merchants authorize your client at auth.lsk-prod.app, you exchange the code at the token endpoint, and you refresh before the 25-minute access token expires. Client ids are environment-specific.
Are there webhooks?
Yes. The Order and Pay webhook, set through PUT /o/wh/1/webhook, always sends account CLOSED and CHECK_WAS_UPDATED, order FAILURE, READY_FOR_PICKUP, and CANCELLED, and payment SUCCESS and FAILURE; DELIVERED and SALES_RESTRICTION_UPDATED are opt-in. The Staff API sends shift.created, shift.updated, and shift.deleted.
Should I use Financial V1 or V2?
V2 (/f/v2/...) sorts by timeClosed, excludes unclosed transactions, and pages by nextPageToken with 100 sales per page. V1 (/f/finance/...) still supports historical dating of back-office transactions, so Lightspeed says V1 may suit reconciliation by original business date until V2 adds it.
Ask about Lightspeed Restaurant

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Lightspeed Restaurant through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy