Query the Lightspeed Restaurant POS (O-Series/Kounta) API using regular SQL

You're a developer. You're perfectly capable of connecting to the Lightspeed Restaurant POS (O-Series/Kounta) API and pulling down data. But why waste your time building an API integration when your skills and time are better spent elsewhere?

API integrations are hard to build and maintain. But with SyncHub, you can query your data source using a language you know and love - SQL.

How it works

Get your Lightspeed Restaurant POS (O-Series/Kounta) data into your favourite reporting tool in just two minutes and three easy steps.

1 2 3 Connect Lightspeed Restaurant POS (O-Series/Kounta) to SyncHub

Securely connect your cloud software to SyncHub and we'll do the rest.

1 2 3 We sync your data automatically

SyncHub incrementally syncs your data and stages it in a managed data warehouse. We check for changes so you don't have to.

1 2 3 Connect your reporting tool

Use reporting tools like Excel, Tableau or Power BI to connect to your data warehouse and build sophisticated reports and dashboards.

No ODBC driver required

SyncHub runs in the cloud, 24×7. There are no ODBC drivers to install or maintain, and no local computer required to cache your results. Just securely connect SyncHub to your Lightspeed Restaurant POS (O-Series/Kounta) account and you can be querying your data in just a couple of minutes.

BYOD

Want more power? How about views, stored procedures or triggers? No problem - SyncHub's Bring Your Own Database feature gives you complete control over your database.

Real-time data*

Make a change in Lightspeed Restaurant POS (O-Series/Kounta) and query it via SQL within minutes. Our feed is so quick, you'll think you're querying Lightspeed Restaurant POS (O-Series/Kounta) directly!

Your data is secure

Your Lightspeed Restaurant POS (O-Series/Kounta) data is stored using best-practice security protocols. But if you're still concerned, no worries - just use our BYOD (Bring Your Own Database) option when setting up your account.

Frequently asked questions

Not directly, no. But SyncHub's ERD model, combined with the real-time* sync from Lightspeed Restaurant POS (O-Series/Kounta), means that it is essentially the same as querying directly.
No. Our solution is cloud-hosted, meaning no installs are required on your own computers. Furthermore, because it is cloud-hosted, SyncHub runs in the background 24-7, keeping your data up to date while you sleep.
SyncHub can poll Lightspeed Restaurant POS (O-Series/Kounta) as frequently as every five minutes, however this capability may be limited by the amount of data you have and/or the type of plan you have with Lightspeed Restaurant POS (O-Series/Kounta). The best way to find out is to simply grab a free trial of SyncHub, connect Lightspeed Restaurant POS (O-Series/Kounta), then see for yourself.
No. SyncHub is a reporting tool and cannot reflect changes back to your cloud application.
We currently sync Category, Customer, Customer tag, Employee, Inventory, Modifier, Order, Order item, Payment, Payment method, Price list, Product, Product category, Product price, Product site, Product tag, Purchase order, Purchase order item, Reconciliation, Reconciliation payment method, Reconciliation revenue (account - amount), Reconciliation revenue (account), Reconciliation revenue (layby - amount), Reconciliation revenue (layby), Reconciliation revenue (sale - amount), Reconciliation revenue (sale), Register, Reporting group, Reporting group product, Site and Table (see our Data Model for full details). If there's something else you need just ask.
Your Lightspeed Restaurant POS (O-Series/Kounta) data is stored in its own dedicated data warehouse, hosted in our Microsoft Azure Sydney Data Center. If you'd like it stored somewhere else (even your own servers), just enquire about our BYOD (bring-your-own-database) option.
Absolutely. Every customer gets their very own isolated data warehouse. Database credentials are salt-encrypted...multi-factor authentication can be activated for your account...we take security very seriously.

Example queries

Check out these example queries for some inspiration

  • select pt.Tag, pt.ProductID, p.Price, p.Deleted from [kounta].ProductTag pt left join [kounta].Product p on pt.ProductRemoteID = p.RemoteID
  • select ps.IsAvailable, ps.IsInventory, p.Price, p.Deleted from [kounta].ProductSite ps left join [kounta].Product p on ps.ProductRemoteID = p.RemoteID
  • select ct.TagName, ct.CustomerID, c.FullName, c.AvatarURL from [kounta].CustomerTag ct left join [kounta].Customer c on ct.CustomerRemoteID = c.RemoteID
  • select top 8 IsRefund, SaleID, RemoteSiteID, RemoteStaffMemberID, Tax, Tip from [kounta].Order order by IsRefund
  • select top 9 ProductID, OrderID, UnitPriceGross, PriceFixedVariation, PriceVariation, LineTotalTax from [kounta].OrderItem order by ProductID
  • select top 5 Price, Deleted, IsSold, Measure, UnitOfMeasure, MaxSellPrice from [kounta].Product order by Price
* Realtime

SyncHub's engine polls for changes every 5 minutes. However, different APIs, and different endpoints within those APIs, may impose restrictions beyond our control - thereby reducing the fidelity of your real-time feed.