Your till knows more about your business than anything else you own. Every sale, every refund, every product, every booking, every shift. But a lot of the time that information needs to be somewhere else too: with your accountant, in a head-office dashboard, in a reporting tool, in your marketing system.
Until now, getting it there meant exporting a report, saving a spreadsheet, emailing it across and doing it all again next week. Today that changes. The epos247 API is live, and it lets the other systems you use read your epos247 data directly, safely and automatically.
What is an API, in plain English?
An API is a secure doorway that lets one piece of software talk to another. With the epos247 API, you give a system you trust a key, and that system can then fetch the information you've allowed it to see, whenever it needs it, without anyone pressing "export".
You don't need to be technical to use it. You create the key in Back Office in about five minutes, and hand it to whoever is building the connection: your accountant, your IT person, your reporting company or your head office.
What it can read
You decide what each connection can see, ticking only what it needs:
- Sales: every sale and refund, with the items, the payments and totals for any date range.
- Products: your products, categories, groups, prices and payment methods, with cost prices if you choose to share them for margin analysis.
- Stock: stock levels and every stock movement.
- Customers: anonymised by default, or with names and contact details only if you specifically allow it.
- Bookings: table bookings with the date, time, party size and status.
- Staff: staff names and roles, who served each sale, and clock in and out times. Never PINs and never pay rates.
- Cash movements: paid in and paid out records.
What it means for your business
No more exporting spreadsheets. The weekly ritual of downloading reports and emailing them on is gone. The systems that need your figures fetch them themselves, and they're always up to date.
Your accountant gets what they need, without chasing you. Give your accountant or bookkeeper a key that reads sales and cash movements, and they can pull your takings, payment types and paid outs straight into their own tools whenever they need them.
Head offices see every site in one place. Running a group of pubs, a chain of cafés or a franchise? A reporting system can read every venue and put them side by side in one dashboard. Each venue approves the connection, so nobody's data is shared without their say-so.
Use the reporting tools you already love. epos247's own reports are comprehensive, but if your business already lives in Power BI, a data warehouse or a specialist hospitality analytics service, your epos247 figures can now sit right alongside everything else.
Connect the rest of your business. Clock in and out times can feed payroll. Stock movements can feed purchasing and forecasting. Bookings and anonymised customer behaviour can feed your marketing. If a system can read data over the internet, it can work with epos247.
It's your data, and you're never locked in. We think the information your business creates belongs to you. The API means you're free to use it however and wherever it helps you most.
Secure by design, and you're always in charge
- Read-only. The API can look but never touch. Nothing connected through it can change a price, a sale, a customer or anything else in your epos247, and your tills carry on exactly as before.
- Nothing is shared until you say so. Only the account owner can create keys, and each key reads only what you've ticked.
- One key per connection. Give each system its own key, so you can see exactly what each one uses and switch one off without touching the others.
- Switch it off instantly. Revoke a key in Back Office and that connection stops straight away.
- Customer privacy built in. Customer details are anonymised unless you deliberately allow names and contact details, and Back Office asks you to confirm you're allowed to share them before it lets you.
- Keys are treated like passwords. A key is shown once when you create it. We keep no copy, and we'll never ask you for it.
- Sensible limits. Every key has a fair daily allowance, so a badly built connection can't run away with itself. If a genuine use needs more, we can raise it.
Built for developers, too
If you're the one building the connection, you'll feel right at home. It's a straightforward REST API returning JSON, with an API key in a header, clear paging, date filters, and a summary endpoint for totals. There's a step-by-step API guide that takes you from key to first request with working examples, and a full API reference listing every endpoint, field, limit and error.
How to get started
- Ask us to switch on API Access. It's an add-on we switch on per venue. Email support@epos247.com from the address you use to log in to Back Office and tell us which venue it's for.
- In Back Office, go to Settings → API Access and choose Create a key.
- Give it a name you'll recognise, such as "Accountant's dashboard", tick what it can read, and create it.
- Copy the key and send it privately to whoever is building the connection, along with the address shown on the page. Point them at the API guide and they'll take it from there.
Not sure whether the API is right for what you have in mind, or working with a reporting company or software partner who'd like to connect to epos247? Get in touch with your account manager or our support team and we'll happily talk it through.