Commerce & Payments · Integration
Ecwid by Lightspeed
Add Ecwid by Lightspeed to your product for your customers, and give your AI agents governed access to it.
Every Ecwid call carries the numeric store id in the path, as in app.ecwid.com/api/v3/{storeId}/products, and the token is scoped to that one store, so a multi-store customer is several connections rather than one. Public apps authenticate by OAuth and receive only the scopes they declared, such as read_catalog or update_orders, and a call outside those scopes fails at the gateway rather than at the resource. Product variants are called combinations and live on a sub-resource of the product, each with its own SKU, price and inventory, so stock syncs that only write the parent product quietly miss the variant level. Orders expose both a numeric id and a customer-facing order number, and webhook payloads reference the former while support tickets quote the latter. Apps can also store their own JSON against a store or a product through the application storage endpoints, which avoids a shadow database for per-store settings. fastn holds each store's token, keeps the OAuth grant refreshed, and keeps store ids mapped to your tenants without you building that layer.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Ecwid store so your app reads their live catalogue and orders.
Sync stock and pricing down to the combination level so variants stay accurate.
Create or update orders from your system and reflect fulfilment status back into Ecwid.
Read customer records and order history to power segmentation inside your own product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent answer catalogue and order questions for a store, with every read scoped and audited per tenant.
Have an agent find products whose variants are out of stock while the parent still shows as available.
Allow an agent to draft price changes for review rather than writing them straight to the catalogue.
Example prompt
Which Ecwid products have variants that are out of stock but still listed as available?
Set up Ecwid by Lightspeed in 4 steps
- 01Enable the Ecwid by Lightspeed connector from your fastn dashboard.
- 02Have each customer authorise their own Ecwid by Lightspeed account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Ecwid by Lightspeed integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Ecwid by Lightspeed integration without building it. Your customers connect their own Ecwid by Lightspeed account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Ecwid by Lightspeed update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ecwid by Lightspeed connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Ecwid by Lightspeed, across other categories.
NetSuite
Notion
Box
DocusignEcwid by Lightspeed integration FAQ
How do I add an Ecwid by Lightspeed integration to my product?
Enable the Ecwid by Lightspeed connector in your fastn dashboard, then let each customer authenticate their own Ecwid by Lightspeed account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ecwid by Lightspeed client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ecwid by Lightspeed account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ecwid by Lightspeed account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Ecwid by Lightspeed integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent answer catalogue and order questions for a store, with every read scoped and audited per tenant.
Who maintains the Ecwid by Lightspeed integration?
fastn does. When Ecwid by Lightspeed changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Ecwid by Lightspeed integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Ecwid by Lightspeed integration?
A common starting point: let a customer connect their own Ecwid store so your app reads their live catalogue and orders. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Ecwid by Lightspeed integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ecwid by Lightspeed does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ecwid by Lightspeed to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.