Reference · built on requestConnectorHospitality & property systems

Oracle MICROS Simphony

Checks, menus, discounts, tenders, locations, and employees from Oracle MICROS Simphony through Transaction Services Gen2.

Request accessPricing ↗

About

Oracle MICROS Simphony is a restaurant point of sale from Oracle. Simphony Transaction Services Gen2 (STS Gen2) is its REST interface for Simphony Standard Cloud Service customers hosted on the Oracle Hosting Center, offered as a cloud endpoint or as a location endpoint on a workstation. It exposes organizations, locations, revenue centers, menus, discounts, service charges, tenders, taxes, checks, employees, and event notifications.

Through Fibric, an operator reads open checks and menu availability per revenue center and proposes a check, a round, or a totals calculation for your approval. Approved changes run once and leave a receipt that says what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Oracle MICROS Simphony and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Open checks per revenue center through GET /api/v1/checks, with checkEmployeeRef, orderTypeRef, tableName, sinceTime, and includeClosed filters
  • A single check with menu items, discounts, service charges, taxes, tenders, and totals through GET /api/v1/checks/{checkRef}
  • Menus and menu summaries through GET /api/v2/menus/{menuId} and /api/v2/menus/summary, plus unavailable items through /api/v1/menus/items/unavailable
  • Discount, service charge, and tender collections, tax definitions, and the barcode collection through the Configuration API
  • Organizations, locations, and revenue centers through /api/v1/organizations/{orgShortName}/locations/{locRef}/revenueCenters
  • Employee numbers through GET /api/v1/employees
  • CheckNotification, ConfigurationNotification, OrganizationsNotification, and EmployeesNotification events through Notifications API subscriptions

Proposed actions

  • Target capability: propose a new check through POST /api/v1/checks
  • Target capability: propose a round of items on an open check through POST /api/v1/checks/{checkRef}/round
  • Target capability: propose a totals calculation before commit through POST /api/v1/checks/calculator
  • Target capability: propose deleting a check through DELETE /api/v1/checks/{checkRef}
  • Target capability: propose a notification subscription through POST /api/v1/notifications/subscriptions

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Watch open checks by table

    GET /api/v1/checks with tableName and sinceTime shows which tables are still open and for how long. The operator proposes the follow-up a manager should make.

    With Table No-Show, Service Recovery

  • Keep unavailable items off the menu

    The unavailable items collection and ConfigurationNotification events show what has been marked out. The operator proposes the online menu change and records the reason.

    With 86 Watch

  • Forecast covers per revenue center

    Closed checks with includeClosed=true give history per revenue center. The operator builds the cover forecast and proposes prep and staffing levels.

    With Cover Forecast

  • Reconcile tenders to deposits

    Tenders and totals on each check give the daily take by tender type. The operator matches them to bank deposits and proposes the entries to review.

    With Bank Reconciliation

Requirements

  • Simphony Standard Cloud Service hosted on the Oracle Hosting Center, with STS Gen2 provisioned by Oracle
  • An API account of type Simphony Transaction Services, created in Oracle Identity Management, with its password set from the welcome email
  • The STS Gen2 service URL and OpenID Connect endpoint from EMC, Enterprise Parameters, Applications
  • Simphony-OrgShortName, Simphony-LocRef, and Simphony-RvcRef headers on each request
  • STS Gen2 enabled for the revenue centers and workstations that will receive checks
Authentication
OpenID Connect authorization code with PKCE at {HOST}/oidc-provider/v1/oauth2/token using the Client ID of a Simphony Transaction Services API account; the id_token is sent as a Bearer and lasts 14 days, the refresh token 28 days.

Limits

  • GET /api/v1/checks returns open checks by default; closed checks appear only with includeClosed=true
  • EmployeesNotification subscribes at organization and property level only, not revenue center
  • Webhook deliveries carry a Digest header, an HMACSHA256 of the body with the subscriber key, that the receiver must check
  • Oracle recommends at least two POS API client workstations per revenue center when using the cloud endpoint

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Oracle MICROS Simphony ↗

Questions and answers

What is the difference between the cloud and location endpoints?
Both expose the same STS Gen2 paths. Oracle recommends the cloud endpoint for mobile ordering and off-premises use, and the location endpoint on a workstation for kiosks and on-premises devices that need low latency and keep working when the venue loses connectivity.
How do I authenticate?
Create an API account of type Simphony Transaction Services in Oracle Identity Management. Use its Client ID in an authorization code flow with PKCE against {HOST}/oidc-provider/v1/oauth2/token with scope openid and orgname. The id_token lasts 14 days; Oracle suggests renewing 3 to 7 days before expiry.
Are there event notifications?
Yes. GET /api/v1/notifications/discovery lists CheckNotification, OrganizationsNotification, ConfigurationNotification, and EmployeesNotification. You register an integrator, create subscriptions at organization, property, or revenue center level, and receive signed POSTs with Digest and Key-Id headers.
Ask about Oracle MICROS Simphony

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Oracle MICROS Simphony through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy