← Back to all docs

EPOS Now API

EPOS Now is a cloud-based point-of-sale platform for retail and hospitality businesses, combining POS hardware, integrated payments, inventory, staff management, reporting, and a 100+ app AppStore. Its REST API lets you programmatically read and write products, categories, customers, transactions, stock, bookings, and staff data—so you can sync sales and inventory, push orders, and reconcile reporting across your stack.

By Alex KlarfeldMay 30, 2026
EPOS Now API

What is EPOS Now?

EPOS Now is an all-in-one cloud-based point-of-sale system that helps retail and hospitality businesses simplify sales, track stock, and grow faster. Merchants use EPOS Now to process sales and payments, manage real-time inventory, run staff scheduling and training, surface real-time reporting on sales, margin, customers, and stock, and extend their setup through an AppStore of 100+ integrations spanning accounting, ecommerce, loyalty, scheduling, and online ordering.

Core product areas include:

  • POS Hardware (Countertop, Micro, Pro+, and Duo terminals)
  • Payment Solutions (Air, Link, and Pro+ card machines with integrated processing)
  • Cloud POS Software (back-office management accessible from any device)
  • AppStore Integrations (Shopify, Sage, QuickBooks, OpenTable, Deputy, Loyalzoo, KDS, and 100+ more)

Common data entities:

  • Products, Categories, Brands, Tax Rates, Product Composition
  • Customers, Addresses, Customer Types, Loyalty Points, Credit
  • Transactions, Transaction Items, Tenders, Discounts, Seating Areas
  • Product Stock, Transfers, Purchase Orders, Suppliers, Locations
  • Bookings, Booking Customers, Booking Items
  • Staff, Access Rights, Clocking Records, Devices, End-of-Day Reports

The EPOS Now Integration Challenge

Merchants run daily operations on EPOS Now across retail and hospitality, but turning device- and back-office-driven workflows into reliable API automation is non-trivial:

  • API Device provisioning: Access requires registering an API Device in the EposnowHQ Backoffice and gathering an access key and token before any request can be made
  • Per-merchant configuration: Products, tax rates, seating areas, and staff access rights are configured per location, so generic integrations break across tenants
  • Resource sprawl: Product, Customer, Transaction, Stock Control, Booking, Staff, and Reports each carry their own object models and IDs to reconcile
  • Retail and hospitality differences: A grocery store's stock and pricing flows look nothing like a restaurant's bookings, seating, and KDS workflows
  • Format and pagination handling: The API accepts and returns both JSON and XML, and large product, customer, and transaction sets require careful paging
  • AppStore overlap: Some capabilities are brokered through AppStore partner apps rather than direct endpoints, adding indirection to integrations

How Supergood Creates EPOS Now APIs

Supergood reverse-engineers EPOS Now's authenticated REST surface and Backoffice flows to deliver a resilient, normalized API layer for your EPOS Now account—across retail and hospitality configurations.

  • Handles API Device access key/token credentials securely in a managed session
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across Products, Customers, Transactions, Stock Control, Bookings, and Staff so you integrate once and rely on consistent objects
  • Aligns with per-location product, tax, and access-rights configuration to ensure correct, scoped access

Use EPOS Now with AI agents: EPOS Now MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your locations, retail or hospitality workflows, and API Device credentials.

  • Supergood Generates and Validates Your API

We deliver a production-ready EPOS Now adapter tailored to your account configuration and access rights.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as EPOS Now evolves.

eposnow

API Endpoints

Authentication

POST/authenticate

Authenticate to an EPOS Now account using API Device access key and token credentials and obtain a session for downstream calls.

Products

GET/products

List products with categories, brands, tax rates, and composition, filtered by location, category, and status.

Products

POST/create_product

Create a new product with pricing, tax rate, category, and stock settings for a given location.

Transactions

GET/transactions

Retrieve transactions with items, tenders, discounts, and seating area details across date ranges and devices.

Customers

GET/customers

Pull customer profiles, addresses, types, loyalty points, and credit balances.

Stock Control

GET/stock

Read product stock levels, transfers, purchase orders, and suppliers across locations.

Use Cases

Sync sales and transactions into your warehouse

- Pull transactions, items, tenders, and discounts from every location into a single warehouse - Stream sales and margin data to downstream BI and finance tools - Reconcile end-of-day and daily sales reports against accounting systems

Keep products and inventory in sync

- Push product, pricing, and tax-rate updates into EPOS Now from a central catalog - Pull real-time stock levels, transfers, and purchase orders for replenishment - Surface low-stock and supplier events to ordering workflows

Unify customer and loyalty data

- Sync customer profiles, addresses, and types into your CRM - Reconcile loyalty points and credit balances across locations - Trigger marketing and retention workflows on new or returning customers

Automate hospitality bookings and staff workflows

- Pull bookings, booking customers, and booking items for reservation systems - Sync staff profiles, access rights, and clocking records to scheduling and payroll - Route seating and booking changes to KDS and front-of-house tools

Technical Specifications

Authentication

API Device access key and token credentials handled in a managed session

Connectivity

EPOS Now REST API plus authenticated Backoffice flows where direct endpoints are not exposed

Response format

Normalized JSON across Products, Customers, Transactions, Stock Control, Bookings, and Staff objects (XML also supported upstream)

Rate limits

Adaptive throttling tuned to your account to avoid EPOS Now-side limits

Session management

Automatic session refresh, credential rotation, and access-key handling

Data freshness

Near real-time pulls for transactions, stock, and customers with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for new transactions, stock changes, customer updates, and bookings

Latency

Sub-second reads on cached entities; multi-second writes when posting products and stock adjustments

Throughput

Horizontally scaled workers sized to multi-location retail and hospitality volume

Reliability

Retry, backoff, and idempotency keys for product, stock, and transaction writes

Adaptation

Continuous monitoring of EPOS Now API releases, AppStore changes, and per-account configuration drift

Frequently asked questions

Yes. Supergood normalizes data across retail flows (products, stock, suppliers) and hospitality flows (bookings, seating areas, KDS), so you integrate once whether you run a store, a restaurant, or both.

EPOS Now access is granted through an API Device registered in the EposnowHQ Backoffice, which provides an access key and token. Supergood works with those credentials and manages the session for you.

Yes. Products, stock, transactions, and staff are pulled and reconciled across every location on your account, with per-location configuration preserved rather than flattened into a generic schema.

Yes. In addition to reads, the API supports creating and updating products, pricing, tax rates, and stock so you can drive EPOS Now from a central catalog or replenishment system.

Where capabilities are brokered through AppStore partner apps rather than direct endpoints, Supergood works against the same authenticated surfaces so your integration behaves consistently regardless of the path.

Ready to get a real API?