Lightspeed
Lightspeed (Lightspeed Commerce) operates a portfolio of Retail, Restaurant, eCom, and Golf POS platforms via series-named product lines: X-Series (Vend), R-Series (Retail Pro/Cloud), C-Series (eCom), E-Series (Ecwid), K-Series (Restaurant Lightspeed), L-Series, O-Series (Kounta), G-Series (Gastrofix), and the ChronoGolf Partner API.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Lightspeed the way a machine reads it — 315 machine-readable artifacts across 27 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lightspeed scores 46.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Lightspeed
Each block below is one kind of artifact we hold for Lightspeed. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Lightspeed eCom C-Series API
REST API for the Lightspeed eCom C-Series storefront platform.
Lightspeed eCom E-Series API (Ecwid)
REST API for Ecwid-powered Lightspeed eCom E-Series stores.
Lightspeed Restaurant L-Series API
REST API for the Lightspeed Restaurant L-Series cloud POS.
Lightspeed Restaurant O-Series API (Kounta)
REST API for Lightspeed Restaurant O-Series (Kounta).
Lightspeed Restaurant G-Series API (Gastrofix)
REST API for Lightspeed Restaurant G-Series (Gastrofix).
Lightspeed ChronoGolf Partner API
Partner API for ChronoGolf, Lightspeed's tee-time and course management platform.
Lightspeed Account API
The Lightspeed Retail account associated with the access token.
Lightspeed Brands API
The Brands API from Lightspeed — 2 operation(s) for brands.
Lightspeed Catalog API
Categories, manufacturers, and vendors that classify items.
Lightspeed Customer API
Customer records and contact details.
Lightspeed Customers API
The Customers API from Lightspeed — 2 operation(s) for customers.
Lightspeed Financial API
V1 endpoints (`/f/finance/...`) for retrieving sales and financial data. For the newer V2 versions of these endpoints see FinancialV2 ### V1 behaviour - **Sorting**: No guarante...
Lightspeed FinancialV2 API
V2 endpoints (`/f/v2/...`) for retrieving sales and financial data. ### Endpoint Mapping | V1 Endpoint | V2 Endpoint | |-------------|-------------| | `getFinancials` (`/f/finan...
Lightspeed Gift Cards API
The Gift Cards API from Lightspeed — 1 operation(s) for gift cards.
Lightspeed ID Cards API
The ID Cards API from Lightspeed — 2 operation(s) for id cards.
Lightspeed Item API
Inventory items sold and tracked in Lightspeed Retail.
Lightspeed Items API
The Items API from Lightspeed — 2 operation(s) for items.
Lightspeed Order and Pay API
The Order and Pay API from Lightspeed — 18 operation(s) for order and pay.
Lightspeed Order and Pay: Webhook API
The Order and Pay: Webhook API from Lightspeed — 4 operation(s) for order and pay: webhook.
Lightspeed PMS API
The PMS API from Lightspeed — 3 operation(s) for pms.
Lightspeed Products API
The Products API from Lightspeed — 2 operation(s) for products.
Lightspeed Reservations for Platforms API
The Reservations for Platforms API from Lightspeed — 11 operation(s) for reservations for platforms.
Lightspeed Rich Item API
The Rich Item API from Lightspeed — 6 operation(s) for rich item.
Lightspeed Sale API
Point-of-sale transactions and their line items.
Lightspeed Sales API
The Sales API from Lightspeed — 2 operation(s) for sales.
Lightspeed Staff API
Staff API. Authorisation Code grant type is required for this API with permission ROLE_CONFIG_USERS.
Lightspeed Tax Breakdown API
The Tax Breakdown API from Lightspeed — 1 operation(s) for tax breakdown.
Scroll within the panel for all 27 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Lightspeed Restaurant K Series API
OPEN COLLECTIONLightspeed Retail R-Series API
OPEN COLLECTIONLightspeed Retail X-Series API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lightspeed Pos Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Lightspeed Pos Finops
FINOPSSemantic Vocabularies 3
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Lightspeed API Rules
SPECTRALLightspeed API Rules
SPECTRALJSON Schema 94
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
apeAccountProfile
JSON SCHEMAapeAccountProfiles
JSON SCHEMAapeAccountSnapshot
JSON SCHEMAapeBusinessLocationId
JSON SCHEMAapeCustomerInfo
JSON SCHEMAapeDiscount
JSON SCHEMAapeLocalOrderItemLine
JSON SCHEMAapeMenu
JSON SCHEMAapeMenuV2
JSON SCHEMAapeOrderPayment
JSON SCHEMAapePaymentBadRequestError
JSON SCHEMAapePaymentSubmissionResponse
JSON SCHEMAapeProductionInstruction
JSON SCHEMAapeRestrictedItemPaginatedResponse
JSON SCHEMAapeSkusRequest
JSON SCHEMAapeStandalonePayment
JSON SCHEMAapeTable
JSON SCHEMAapeToGoOrderItemLine
JSON SCHEMAapeWebhookEndpointBusinessLocationDto
JSON SCHEMAapeWebhookEndpoint
JSON SCHEMAfinancial-apiAbortedOrderDto
JSON SCHEMAfinancial-apiFinancialDto
JSON SCHEMAfinancial-apiLSPaymentsDto
JSON SCHEMAfinancial-apiResourcesTaxRate
JSON SCHEMAfinancial-apiSaleDto
JSON SCHEMAfinancial-apiSalesDailyExportDto
JSON SCHEMAfinancial-apiSalesExportDto
JSON SCHEMAid-cards-apiCreateIdCardBatchRequest
JSON SCHEMAid-cards-apiCreateIdCardsRequest
JSON SCHEMAid-cards-apiCreateIdCardsResponse
JSON SCHEMAid-cards-apiIdCardBatch
JSON SCHEMAitems-apiCreateItemDTO
JSON SCHEMAitems-apiItemDTO
JSON SCHEMAitems-apiUpdateItemDTO
JSON SCHEMApms-apiBusinessLocationId
JSON SCHEMApms-apiGetProvider
JSON SCHEMApms-apiProviderApiKey
JSON SCHEMApms-apiProviderEndpoint
JSON SCHEMApms-apiProviderFeatures
JSON SCHEMApms-apiProviderName
JSON SCHEMApms-apiRevenueCenterId
JSON SCHEMApms-apiRevenueCenterName
JSON SCHEMAreservation-serviceOnboardingCallbackRequest
JSON SCHEMAreservation-servicePlatformAPIKeysWebhook
JSON SCHEMAreservation-servicePlatformBasicAuthWebhook
JSON SCHEMAreservation-servicePlatformBusinessLocation
JSON SCHEMAreservation-servicePlatformCourseSettingsDto
JSON SCHEMAreservation-servicePlatformIntegrationDto
JSON SCHEMAreservation-servicePlatformOAuth2Webhook
JSON SCHEMAreservation-servicePlatformProfileResponse
JSON SCHEMAreservation-servicePlatformProfile
JSON SCHEMAreservation-servicePlatformReservation
JSON SCHEMAstaff-apiBOStaff
JSON SCHEMAstaff-apiBusinessLocationIds
JSON SCHEMAstaff-apiCreatePosStaffDto
JSON SCHEMAstaff-apiCreateWebhookRequest
JSON SCHEMAstaff-apiPOSStaff
JSON SCHEMAstaff-apiReportAccessLevel
JSON SCHEMAstaff-apiResponseSchema
JSON SCHEMAstaff-apiShift
JSON SCHEMAstaff-apiStaffGroup
JSON SCHEMAstaff-apiStaff
JSON SCHEMAstaff-apiUpdatePosStaffDto
JSON SCHEMAstaff-apiUserPermission
JSON SCHEMAstaff-apiWebhookDto
JSON SCHEMAteckelLinkSelfPage
JSON SCHEMAteckelLinkSelf
JSON SCHEMAteckelLocalesDto
JSON SCHEMAteckelPictureSpecDto
JSON SCHEMAteckelRichItemDescriptionDto
JSON SCHEMAteckelRichItemDtoDates
JSON SCHEMAteckelRichItemDtoLinks
JSON SCHEMAteckelRichItemDtoPictures
JSON SCHEMAteckelRichItemDto
JSON SCHEMAAccount
JSON SCHEMAAttributes
JSON SCHEMACategory
JSON SCHEMAContact
JSON SCHEMACustomer
JSON SCHEMAEmployee
JSON SCHEMAItem
JSON SCHEMAManufacturer
JSON SCHEMASaleLine
JSON SCHEMASale
JSON SCHEMAShop
JSON SCHEMAVendor
JSON SCHEMABrand
JSON SCHEMACustomer
JSON SCHEMAProduct
JSON SCHEMASale
JSON SCHEMAScroll within the panel for all 94 ·
JSON Structure 94
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Restaurant K Series Ape Account Profile Structure
JSON STRUCTURERestaurant K Series Ape Account Profiles Structure
JSON STRUCTURERestaurant K Series Ape Account Snapshot Structure
JSON STRUCTURERestaurant K Series Ape Business Location Id Structure
JSON STRUCTURERestaurant K Series Ape Customer Info Structure
JSON STRUCTURERestaurant K Series Ape Discount Structure
JSON STRUCTURERestaurant K Series Ape Local Order Item Line Structure
JSON STRUCTURERestaurant K Series Ape Menu Structure
JSON STRUCTURERestaurant K Series Ape Menu V2 Structure
JSON STRUCTURERestaurant K Series Ape Order Payment Structure
JSON STRUCTURERestaurant K Series Ape Production Instruction Structure
JSON STRUCTURERestaurant K Series Ape Skus Request Structure
JSON STRUCTURERestaurant K Series Ape Standalone Payment Structure
JSON STRUCTURERestaurant K Series Ape Table Structure
JSON STRUCTURERestaurant K Series Ape To Go Order Item Line Structure
JSON STRUCTURERestaurant K Series Ape Webhook Endpoint Structure
JSON STRUCTURERestaurant K Series Financial Api Sale Dto Structure
JSON STRUCTURERestaurant K Series Id Cards Api Id Card Batch Structure
JSON STRUCTURERestaurant K Series Items Api Create Item Dto Structure
JSON STRUCTURERestaurant K Series Items Api Item Dto Structure
JSON STRUCTURERestaurant K Series Items Api Update Item Dto Structure
JSON STRUCTURERestaurant K Series Pms Api Get Provider Structure
JSON STRUCTURERestaurant K Series Pms Api Provider Api Key Structure
JSON STRUCTURERestaurant K Series Pms Api Provider Endpoint Structure
JSON STRUCTURERestaurant K Series Pms Api Provider Features Structure
JSON STRUCTURERestaurant K Series Pms Api Provider Name Structure
JSON STRUCTURERestaurant K Series Pms Api Revenue Center Id Structure
JSON STRUCTURERestaurant K Series Staff Api Bostaff Structure
JSON STRUCTURERestaurant K Series Staff Api Posstaff Structure
JSON STRUCTURERestaurant K Series Staff Api Response Schema Structure
JSON STRUCTURERestaurant K Series Staff Api Shift Structure
JSON STRUCTURERestaurant K Series Staff Api Staff Group Structure
JSON STRUCTURERestaurant K Series Staff Api Staff Structure
JSON STRUCTURERestaurant K Series Staff Api User Permission Structure
JSON STRUCTURERestaurant K Series Staff Api Webhook Dto Structure
JSON STRUCTURERestaurant K Series Teckel Link Self Page Structure
JSON STRUCTURERestaurant K Series Teckel Link Self Structure
JSON STRUCTURERestaurant K Series Teckel Locales Dto Structure
JSON STRUCTURERestaurant K Series Teckel Picture Spec Dto Structure
JSON STRUCTURERestaurant K Series Teckel Rich Item Dto Dates Structure
JSON STRUCTURERestaurant K Series Teckel Rich Item Dto Links Structure
JSON STRUCTURERestaurant K Series Teckel Rich Item Dto Structure
JSON STRUCTURERetail R Series Account Structure
JSON STRUCTURERetail R Series Attributes Structure
JSON STRUCTURERetail R Series Category Structure
JSON STRUCTURERetail R Series Contact Structure
JSON STRUCTURERetail R Series Customer Structure
JSON STRUCTURERetail R Series Employee Structure
JSON STRUCTURERetail R Series Item Structure
JSON STRUCTURERetail R Series Manufacturer Structure
JSON STRUCTURERetail R Series Sale Line Structure
JSON STRUCTURERetail R Series Sale Structure
JSON STRUCTURERetail R Series Shop Structure
JSON STRUCTURERetail R Series Vendor Structure
JSON STRUCTURERetail X Series Brand Structure
JSON STRUCTURERetail X Series Customer Structure
JSON STRUCTURERetail X Series Product Structure
JSON STRUCTURERetail X Series Sale Structure
JSON STRUCTUREScroll within the panel for all 94 ·
Examples 85
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Retail R Series Item Example
EXAMPLERetail R Series Sale Example
EXAMPLERetail R Series Shop Example
EXAMPLERetail X Series Sale Example
EXAMPLEScroll within the panel for all 85 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Lightspeed — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lightspeed-pos · machine-readable index on apis.io