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.