Oracle Simphony API
Simphony has five coexisting API surfaces, from REST Transaction Services Gen 2 to legacy SOAP, all gated behind Oracle's partner program. Each integration must be validated before production, and documentation is scattered across multiple Oracle libraries with version drift.
Frequently asked questions
Oracle Simphony scores F on the API Report Card. Simphony has five coexisting API surfaces, from REST Transaction Services Gen 2 to legacy SOAP, all gated behind Oracle's partner program. Each integration must be validated before production, and documentation is scattered across multiple Oracle libraries with version drift.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Oracle Simphony (formerly MICROS Simphony, acquired by Oracle in 2014 for $5.3B) is Oracle's enterprise cloud-and-mobile restaurant POS and hospitality management platform.
POS / Hospitality - specifically the enterprise tier of restaurants and F&B operations. Servers and bartenders use Simphony for opening checks, ordering at table or counter, splitting/combining checks, applying discounts/comps/voids, sending orders to kitchen displays or printers, processing EMV/NFC payments and tips on Oracle Workstation or Tablet hardware, posting charges to a hotel guest folio (via OPERA), and end-of-shift close.
Oracle MICROS is one of the most ubiquitous enterprise restaurant POS platforms in the world, particularly dominant in hotels and large global chains.
Yes - Simphony is the system of record for revenue, tax, and labor at the property level for some of the largest hospitality operators in the world.
The MICROS lineage is 40+ years old (MICROS Systems founded 1977, Simphony product line launched mid-2000s as the cloud/multi-tenant successor to the on-prem MICROS 9700 and RES 3700 lines). Oracle acquired MICROS in 2014.
Multi-API sprawl - Configuration & Content API, STS Gen 2, legacy SOAP TS, Reporting & Analytics, and JavaScript Extensibility each have different auth, hosts, and conventions; ISVs must support several to deliver one integration. OAuth2 + EBO Open ID Connect (IDM) flow is non-trivial - token scoping for cloud vs on-prem (Client Scope = Both / Local), location-based authorization, and id_token expiration all add friction for new integrators. Full sourced list under Sources below.
Common alternatives include Toast, NCR Voyix Aloha, Square for Restaurants, Par Brink POS (PAR Technology), Lightspeed Restaurant, Agilysys InfoGenesis. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.