← Blog GASTRONOMY

How Simphony Cloud Service Models Affect API Access

Understand the distinction between the cloud service model, account administration and API entitlement in Simphony.

Abstract editorial diagram of Simphony service integration topic

Cloud hosting does not establish who administers access

Two venues can use similar Simphony screens while having different contracts, subscription scopes and support arrangements. One may have an authorised API account administrator; the other may depend on a service provider.

The starting questions are therefore: who provides the service, which API subscriptions apply and who can manage access?

Separate service arrangements from API capability

Oracle's integrations programme supports independent solutions, while its API account guide describes account types and subscriptions that may be additional. Neither source guarantees identical entitlements across every venue.

Ask for the required API product, licensing conditions, administrator, provisioning process and any specific limitation in writing.

A multi-outlet example

Imagine a hotel with three restaurant outlets. Management wants a reservation-to-check pilot in only one. It can define that outlet, its revenue centre and the necessary STS Gen2 permissions before discussing other locations.

If extra licensing or configuration work is needed, request the exact item and activation process. A dated support record helps all parties distinguish delay from a confirmed technical restriction.

Support ownership and API administration are different

A venue may receive day-to-day POS support from a service provider while API account creation and subscription activation follow a separate administration process. Having a cloud subscription does not, by itself, establish a particular API entitlement. Identify the contractual service scope and the administrator authorised to provision access.

For example, if API Accounts is not visible to an authorised venue employee, that does not establish a technical incompatibility. The missing element may be a role, a separate subscription or the service model. Ask the provider to distinguish these possibilities in writing.

Where Rezervem can help

Rezervem's Oracle partnership and existing STS Gen2 integration provide a verified technology option, not an automatic change to the venue's subscription. The version and permissions guide identifies the required facts.

Official Oracle references

Oracle Simphony integrations · STS Gen2 API · API Accounts.

REZERVEM · ORACLE SIMPHONY CLOUD Manager

Connect the visit to the POS check.

Connect validated Simphony transaction workflows with guest and reservation operations.

Assess your integration readiness.

Review your Simphony Cloud environment, API entitlements and supported Rezervem integration workflows.