Gaming Custom

Outbound Type GAMING_CUSTOM is used to integrate OPERA Cloud functionality like Profile Lookup and Download and Create Enrollment with any Gaming/Player Tracking System that follows OPERA Cloud REST APIs specification and standards.

This outbound Type should be used when any gaming vendor has custom integration and message specification transformation requirements. It is implemented using Oracle Integration Cloud (OIC) services.

1. Outbound Code should be created for the Property which requires Scientific Gaming integration.

2. Select Outbound Type GAMING_CUSTOM.

3. Enter a unique outbound code in the format of gaming system code and property code, for example: SGACSCP1.

4. Enter and description for the gaming system name.

5. Enable External System, Enable Conversions, and External Property Code.

6. Protocol is defaulted with REST for custom gaming integration.

7. Select Authorization Type OAUTH and provide OAuth Token URL, for example: https://gaminghost.com/v1/oauth.

8. Select Grant Type Client Credentials, and enter Client Id & Client Key and Application Key provided by the Gaming/Player Tracking System.

9. Enter the RESP API Base URL Service Path provided by gaming vendor, for example: https://gaminghost.com/v1.

10. Save the Outbound Systemconfiguration.

11. Add Data Value Mappings. For more information, see Data Value Mappings.

    • Define the Conversion Codes for Address Type, Gender, Phone Type, State Code, Country Code, Language Code, Profile Type, Title, Membership Level, and Membership Type.