Clover API
Clover is a point-of-sale platform from Fiserv that powers in-store payments, order management, inventory, employees, and customer loyalty across one or many locations. With an unofficial API, you can fetch normalized orders and payments, update items and stock, create customers, and export finance-
What is Clover?
Clover is a POS and commerce platform used by retailers, restaurants, and service businesses. It combines hardware (Station, Mini, Flex, Go) with cloud software for payment acceptance, order management, inventory, staffing, loyalty, and reporting.
Core product families include:
- POS and Payments (card-present and select ecomm flows)
- Orders and Menus/Catalog (items, variants, modifiers, categories)
- Inventory and Stock (multi-location quantities and costs)
- Customers and Loyalty (profiles, marketing opt-ins, gift cards)
- Reporting and Payouts (sales summaries, deposits, fees)
Common data entities:
- Merchants, Locations, and Devices
- Items, Variants, Modifiers, Categories, Taxes, Discounts
- Stock Levels and Cost/Price Rules
- Orders, Line Items, Tips, Service Charges
- Payments, Refunds, Tenders (card, cash, gift)
- Customers, Tags, Addresses, Preferences
- Employees, Roles, Shifts (timecards)
- Batches/Settlements and Payouts
The Clover Integration Challenge
Organizations rely on Clover daily, but turning portal- and device-centric workflows into automated pipelines is hard:
- Entitlements and app plans: Access to APIs differs by merchant plan, installed apps, and partner status; some endpoints are gated or billed.
- Device-first constraints: Many actions are designed to occur on terminals; headless/remote operations can be limited or inconsistently exposed.
- Portal-first exports: CSVs are often daily or filtered views and may omit useful identifiers, making data warehouse feeds brittle.
- Multi-location normalization: Items, prices, and stock can vary by location; IDs, taxes, and discounts differ across terminals and catalogs.
- Data shape complexity: Taxes and discounts can be order- or item-level, tips and service charges vary by restaurant vs retail, and versions differ by merchant.
- OAuth and MFA: Per-merchant authentication with MFA/SSO can break unattended jobs; sessions must be maintained reliably.
- Rate limits and pagination: High-volume syncs require careful batching, backoff, and idempotency.
- Cost/coverage surprises: Developers report unexpected partner fees, limited access to settlement/fee data, and evolving endpoints.
How Supergood Creates Clover APIs
Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your Clover workflows.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses so you can integrate once and rely on consistent objects across capabilities
- Aligns with customer entitlements and licensing constraints to ensure compliant access
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your product mix, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened Clover adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Clover evolves.
API Endpoints
Authentication
/auth/sessionsEstablish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.
Authentication
/auth/sessions/refreshRefresh an existing token to keep sessions uninterrupted.
Orders
/ordersRetrieve normalized orders with line items, taxes/discounts, tips, and payments. Filter by location and time window.
Orders
/ordersCreate or upsert an order with line items, discounts, and customer attachment. When permitted, Supergood can route the order to a device queue for in-store fulfillment.
Inventory
/inventory/itemsList catalog items with variants, modifiers, categories, taxes, and stock by location. Filter by updatedSince for incremental sync.
Customers
/customersCreate or upsert a customer profile with contact details and marketing preferences. Attach your own reference IDs for reconciliation.
Use Cases
Real-Time Order and Payment Sync
- Pull closed and open orders with line items, taxes, discounts, and tips - Ingest payment records with tender types, card brand, last4, and auth references - Stream events into your OMS, CRM, or analytics warehouse
Inventory and Price Governance
- Export catalog items, variants, and modifiers with category and tax mapping - Track and adjust stock by location after ecomm sales or returns - Validate price and tax consistency across terminals and stores
Customer and Loyalty Enrichment
- Create or update customer profiles with marketing opt-ins - Attach customers to orders and segment by tags or spend - Sync gift cards/loyalty identifiers into marketing automation
Payout Reconciliation and Finance
- Aggregate sales, refunds, fees, and deposits for accounting - Align card-present payouts with order- and payment-level detail - Export GL-ready data to accounting and BI systems
Technical Specifications
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination
Rate limits
Tuned for enterprise throughput while honoring licensing and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of orders, payments, inventory, and customers
Security
Encrypted transport, scoped tokens, and audit logging; respects Clover entitlements
Webhooks
Optional asynchronous delivery for order/payment events with retry; polling fallback available
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume, multi-location sync and nightly warehouse exports
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Subject to your licensing and entitlements, Supergood supports POS orders and payments, inventory/catalog, customers/loyalty basics, and reporting/export workflows. We finalize scope during assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling.
We can create cloud orders and, where permitted, queue them to devices. Card-present capture typically remains on-device; we can record non-card tenders and reference third-party ecomm authorizations for reconciliation.
Yes. We normalize items, variants, taxes, and stock by location, preserving per-store differences while providing a consistent schema for downstream systems.
Yes. We aggregate sales, refunds, tips, fees, and deposits into finance-ready exports for accounting and BI, aligned to your settlement cadence and chart of accounts.