The API Report CardAPI Index
Upserve

Upserve API

POS / Hospitality · upserve.com

Two partner-gated REST APIs are documented at api-docs.upserve.com, covering menu, tickets, payments, customers, and inventory. Access requires approval into Lightspeed's partner catalog, and credentials are per-merchant username/password pairs; no OAuth, sandbox, or self-serve signup.

Last verified: July 2026Restaurants & Food Service
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo documented REST APIs at api-docs.upserve.com, POS and Online Ordering, cover menu, tickets, payments, and webhook events.
AccessPOORPartners must be approved into Lightspeed's integration catalog, then each merchant enables the integration; no self-serve signup.
CoveragePOORThird-party ETL vendors like SyncHub exist because the native export and API surface cannot meet operators' reporting needs.
AuthPOORMerchant-scoped username/password pairs instead of OAuth tokens; rotation and multi-tenant handling are painful.
Docs & DXPOORTwo parallel doc sites (bc and olo) with different shapes and auth flows; no sandbox or self-serve signup.
StabilityMIXEDThe APIs are long-published, but the April 2026 divestiture to Skyview Equity puts roadmap and continuity in question.
Supergood: Upserve has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Upserve scores D+ on the API Report Card. Two partner-gated REST APIs are documented at api-docs.upserve.com, covering menu, tickets, payments, customers, and inventory. Access requires approval into Lightspeed's partner catalog, and credentials are per-merchant username/password pairs; no OAuth, sandbox, or self-serve signup.

Tried to integrate with Upserve?
SOURCES
API access is gated behind partner approval - independent developers and restaurant operators cannot obtain credentials without a sponsoring partner relationship api-docs.upserve.com
Credentials are merchant-scoped username/password pairs rather than OAuth tokens, complicating multi-tenant SaaS integrations and credential rotation kb.7shifts.com
Two parallel API surfaces (POS 'bc' and Online Ordering 'olo') with different shapes and authentication flows force partners to maintain two integration paths api-docs.upserve.com
Third-party reporting/ETL vendors (e.g., SyncHub) exist specifically because the native reporting export and API surface are insufficient for operators who want to unlock their own data synchub.io
Future API stability is uncertain following the April 2026 divestiture to Skyview Equity - partners must re-validate roadmap and contractual continuity lightspeedhq.com
POS app lags and crashes during service; printer outages traced to backend software issues with no real-time fix path tech.co
Phone support routinely takes one to two hours on hold and frequently fails to resolve the issue cardpaymentoptions.com
Long-standing feature gaps left unaddressed (no tip entry in offline mode, no per-item preorder controls, weak multi-location menu management) pos.toasttab.com
Hidden fees and lackluster customer service flagged across BBB and merchant review sites bbb.org
Faulty third-party integrations (notably OpenTable) and unmonitored support email channels cardpaymentoptions.com
Product investment perceived as stalled during Lightspeed ownership; FY26 divestiture to Skyview at a fraction of the 2020 purchase price reinforces the perception theglobeandmail.com