Apply for API access through the Lightspeed K-Series API portal and complete the partner agreement before receiving production credentials
Authenticate using the OAuth 2.0 flow described in the K-Series API docs to obtain a Bearer token scoped to the target business location
Create a webhook subscription by POSTing to the webhook endpoint documented in the K-Series API, specifying your callback URL and the event types you want to receive (for example, order and payment events)
Implement your callback endpoint to receive and acknowledge K-Series webhook payloads for events such as Order DELIVERED, Account CLOSED, and Payment SUCCESS or FAILURE
On order events, use the order identifier from the webhook payload to retrieve full order details via the corresponding GET endpoint in the K-Series API
Rotate and securely store your OAuth credentials; test thoroughly in the K-Series staging environment before requesting production approval
Known gotchas
K-Series API access requires explicit partner approval from Lightspeed; sandbox access is granted separately from production
Webhook event coverage differs between the staff/business-location webhook system (shift events) and the order-and-pay webhook system (order, payment, item events) — subscribe to the correct system for your use case
The K-Series API Postman collection is versioned and updated periodically; verify you are using the current collection before implementation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp