Lightspeed API: connect Lightspeed to your accounts, stock and shipping

What you can do with the Lightspeed API

• Orders from Lightspeed as an invoice in Exact Online, Moneybird or another package
• Keep stock in sync between point of sale, webshop and marketplaces
• Shipping labels through Sendcloud as soon as an order is ready
• Customers to your CRM or mailing list, with consent
• Returns and refunds as a credit note in the accounts

How the integration works

With eCom C-Series you create an API key and secret under the store settings; the integration uses those with Basic Auth on the EU cluster and listens to webhooks for orders, products and customers. With Retail X-Series access goes through OAuth 2.0 with date-based versions in the API and webhooks for sales and stock. In both cases every order gets a fixed reference and the integration respects the limits per five minutes.

Facts about the Lightspeed API

Checked on 2 November 2026 against the official documentation. Limits, prices and versions change; the source is listed per row.

Fact	What the documentation says	Source
Authentication C-Series	API key and secret per store (Basic Auth) on the EU cluster; created under the store settings at Developers.	Lightspeed eCom: Authentication
Rate limits C-Series	300 calls per five minutes, 3,000 per hour and 12,000 per day per key, plus 20 per second. When exceeded, 429.	Lightspeed eCom: Rate limiting
Webhooks C-Series	Customers, orders, invoices, shipments, products, variants, returns and more (created, updated, deleted). Respond within five seconds; ten attempts in 24 hours; with more than half failing, disabled after 50 hours.	Lightspeed eCom: Webhooks
Subscription C-Series	The API requires the Advanced or Professional subscription.	Lightspeed eCom: API documentation
Authentication X-Series	OAuth 2.0 with an app from the developer portal, or personal tokens (Plus plan only). Access token and refresh token with rotation on every renewal.	Lightspeed Retail: Authorization
Rate limits X-Series	300 times the number of registers plus 50 per five minutes; when exceeded, 429 with Retry-After.	Lightspeed Retail: Rate limiting
Version X-Series	Date-based versions (for example 2026-01), a new one every quarter, supported for at least twelve months; v0.9 and v2.0 are deprecated.	Lightspeed Retail: Versioning
E-Series	Runs on the Ecwid platform: 600 calls per minute per token, signed webhooks, API only on paid plans.	Ecwid: API reference
n8n	No built-in node and no community node found; the integration runs through an HTTP step in n8n.	n8n documentation

What you need on your side

• Knowing which Lightspeed you have: eCom C-Series, eCom E-Series or Retail X-Series
• A subscription that includes the API, and an administrator who can create a key or app
• One leading stock: point of sale, webshop or a central system
• Access to the accounts or shipping service on the other side

Where it often goes wrong, and how I prevent it

• Wrong variant: C-Series, E-Series and X-Series have different APIs. First we establish which Lightspeed you have; only then we build.
• Limit per five minutes: C-Series allows 300 calls per five minutes per key. A catch-up run therefore has to be spread; the integration schedules that.
• Webhook disabled: with more than half of deliveries failing, Lightspeed disables a webhook after 50 hours. The integration responds fast and watches the error ratio.
• VAT and discounts: point-of-sale discounts and VAT per country must land correctly in the accounts. I record that up front.

In practice

A Lightspeed integration is not yet listed as In production with me. The approach is the same as for WooCommerce and Shopify: orders with a fixed reference to the accounts, one leading stock, and a notification on every exception.

What it costs

I build a Lightspeed integration as one scoped process for a fixed price, from €750. Maintenance and monitoring are a monthly fee: n8n management from €250 per month, server management €145 per server. In the free assessment we work out your process. All prices and what is included →

What I do not do

• I do not build public Lightspeed apps for the app store; the integration is for your store.
• I do not let two systems lead the stock at the same time.
• I do not build new integrations on the deprecated X-Series versions v0.9 and v2.0.

Frequently asked questions about the Lightspeed API

Does n8n have a Lightspeed node?

No, and no community node was found either. I connect Lightspeed through the official API of your variant with an HTTP step in n8n.

Which Lightspeed variant can you connect?

eCom C-Series, eCom E-Series and Retail X-Series. Each has its own API; in the assessment we establish which one you have and what is possible there.

Which subscription do I need for the API?

For eCom C-Series Lightspeed mentions the Advanced or Professional subscription. With E-Series the API only works on paid plans. With Retail X-Series personal tokens are limited to the Plus plan; an integration through OAuth works with the store's consent.

How many calls does Lightspeed allow?

C-Series: 300 per five minutes, 3,000 per hour and 12,000 per day per key. X-Series: 300 times the number of registers plus 50 per five minutes. Above that a 429; the integration then waits.

Can Lightspeed notify the integration?

Yes. C-Series has webhooks for customers, orders, products, stock and more; X-Series for sales, stock and products. What does not arrive through a webhook, the integration checks at fixed intervals.