Aristocrat Oasis

The following operations are supported as part of this gaming integration product. Only the operations listed below are currently supported.

Table 6-1 APIs

Function How it works Direction

Player Enrollment

  • OPERA Cloud sends the name and address information for a new player profile or an existing OPERA Cloud profile to OASIS 360.

  • OASIS 360 creates a player profile and responds to OPERA Cloud with the player ID.

OPERA Cloud–> OASIS 360

Profile Lookup

  • OPERA Cloud users can search OASIS 360 for profile(s) based on Player ID or Last and/or First Name.

  • OASIS 360 returns a list of profiles matching the criteria requested, which the OPERA Cloud user views on-screen.

OPERA Cloud –> OASIS 360

Profile Fetch

  • The OPERA Cloud user selects a profile from a list provided during the Lookup operation.

  • OASIS 360 returns the patron’s name, addresses, birth date, and email address; OPERA Cloud will either insert a new profile record or merge the data into an existing record.

OPERA Cloud –> OASIS 360

Profile Update

OPERA Cloud notifies OASIS 360 of any changes made to the name and/or address, telephone, and email on any OPERA Cloud profile that has an associated OASIS 360 player id.

OPERA Cloud –> OASIS 360

Comp Postings

  • OPERA Cloud sends a comp request to OASIS 360 when a charge is posted to a comp window (101‐108). A comp posting is any charge that was moved to a comp window, regardless of whether it was originally posted manually, through the End of Day sequence, or by POS interface to OPERA Cloud.

  • To void a comp transaction, you must move back to a cash window (1-8). A Void is then sent to OASIS 360.

  • OASIS 360 will either approve or decline the comp posting. Approval status appears on the OPERA Cloud Comp Journal screen.

  • OPERA Cloud sends comp postings to OASIS 360 in monetary value / amount only.

  • OPERA Cloud sends comps monetary value / amount to only one default bucket in OASIS 360.

    Note:

    Do not move transactions between comp windows (101-108).

OPERA Cloud –> OASIS 360

Comp Redemption (payment for window 1-8)

  • Ability in OPERA to obtain a players earned bucket values from the gaming system in order to use as a credit/payment towards their hotel folio balance (cash windows 1-8)

  • OPERA Cloud sends comp redemption to OASIS 360 in monetary value / amount only.

OPERA Cloud –> OASIS 360

Player Snapshot/ PTS Inquiry (view only)

  • OPERA Cloud users can view basic, real-time balances and account information by sending a Player Statistics request from OPERA Cloud to OASIS 360. This information is never stored in OPERA Cloud.

  • OASIS 360 responds with details that appear on Players Statistics screen in OPERA Cloud. For example, comp dollar or points balance.

  • The scope of data sent is not configurable in OPERA Cloud.

OPERA Cloud –> OASIS 360

Player Promotions/Offers (view only)

  • Promotion/Offer codes must be created for both OPERA Cloud and OASIS 360.

  • OPERA Cloud users can click Fetch Offer from the Look to Book screen to view promotions/offers available for the player.

OPERA Cloud –> OASIS 360

Required Information

To invoke the nConnect APIs from OPERA Cloud, you must provide the following nConnect OAuth credentials:

  • URL for Identity Server

  • Client ID

  • Client Secret

  • URL for nConnect Server

  • Username and Password

  • Scope

The integration between OPERA Cloud and nConnect uses the following APIs with their required permissions. nConnect requires these permissions to successfully execute the operations (see list of operations above).

Table 6-2 APIs

API Method Permission

/api/v1/PlayerInfo/

POST

AddPlayerPermission

/api/v1/PlayerInfo/

GET

GetPlayerPermission

/api/v1/PlayerInfo/{PlayerID}/Statistics

GET

GetPlayerStatisticsPermission

/api/v1/PlayerInfo/{playerId}/MarketingCouponsWithPlayerID

GET

GetPlayerMarketingCouponsPermission

/api/v1/PlayerInfo/{playerId}/Accounts/AccountType/{accountType}

GET

GetPlayerAccountBalanceByAccountTypeIdPermission

/api/v1/PlayerInfo/{playerId}/Transactions

POST

AddPlayerTransactionPermission

/api/v1/PlayerInfo/{{playerId}}/Accounts

GET

GetPlayerAccountBalancePermission

/api/v1/PlayerInfo/{playerId}

PUT

UpdatePlayerProfilePermission

/api/v1/PlayerInfo/{playerId}

GET

GetPlayerPermission

/api/v1/PlayerInfo/{playerId}/Address

POST

AddPlayerAddressPermission

/api/v1/PlayerInfo/{playerId}/Address/{addressId}

PUT

UpdatePlayerAddressPermission

/api/v1/PlayerInfo/{playerId}/Email

POST

AddPlayerEmailPermission

/api/v1/PlayerInfo/{playerId}/Email/{emailId}

PUT

UpdatePlayerEmailPermission

/api/v1/PlayerInfo/{playerId}/PersonalID

POST

AddPlayerPersonalIDPermission

/api/v1/PlayerInfo/{playerId}/PersonalID/{ID}

PUT

UpdatePlayerPersonalIDPermission

For further details on nConnect (or Aristocrat Oasis) configurations, email your Aristocrat point of contact or your Oracle Hospitality point of contact.

Parent topic: Gaming Vendor Specific Configurations