Skip to main content

How to Integrate Reality Defender with Genesys Cloud AudioHook

This guide covers integrating Genesys Cloud AudioHook Monitor with Reality Defender for real-time deepfake detection. Use the Session API to retrieve analysis results for your back-end systems or IVR routing logic.

A
Written by Aphrodite Brinsmead
Updated over a week ago

Prerequisites

Before beginning, ensure you have the following:

Requirement

Description

Reality Defender Organization ID

Your unique Reality Defender organization identifier, provided by Reality Defender

Genesys Organization ID

Your unique Genesys Cloud organization identifier, provided by Genesys Cloud

API Key

A generated key of fewer than 255 characters, typically a UUID. Treat this as a sensitive value. May be generated by the customer and shared with Reality Defender, or vice versa

Client Secret

A base64-encoded value. May be generated by the customer and shared with Reality Defender, or vice versa

Before proceeding: Reality Defender requires your Genesys Organization ID to provision the connection on their end. Share it with your Reality Defender customer success representative before beginning this setup.

Note: By default, Reality Defender begins analyzing audio as soon as the connection is established. However, the connection can be configured to wait for a recording.start API call, giving you greater control over which sessions are recorded and analyzed. Refer to the Reality Defender Session API documentation for details.


Step 1: Log In to Genesys Cloud Admin

  1. Open your browser and navigate to Genesys Cloud.

  2. Enter your admin credentials and click Log In.

  3. Select Collaborate / Communicate.


Step 2: Install the AudioHook Monitor from AppFoundry

  1. In the Genesys Cloud Admin portal, enter AppFoundry in the search box and select it.

  2. In the AppFoundry search bar, type AudioHook Monitor.

  3. Locate and click the Genesys AudioHook Monitor tile.

    • If the tile displays Configure, the AudioHook Monitor is already installed β€” proceed to Step 3.

    • If not, review the application details and click Install. Follow the prompts to complete installation.

  4. Sign in to AppFoundry for your region if prompted.


Step 3: Add the AudioHook Monitor Integration

  1. Navigate back to the Genesys Cloud Admin page.

  2. In the search bar, type Integrations and select it.

  3. Click Add Integration on the right-hand side of the page.

  4. Locate the AudioHook Monitor tile from the list of available integrations.

  5. Click Install at the bottom of the tile.


Step 4: Configure the Integration

  1. On the Details tab, enter an integration name (e.g., Reality Defender).

  2. Click on the Configuration tab and enter the following Connection URI:

    wss://app.genesys.os.realitydefender.xyz/audiohook
  3. For Channel, select external.

  4. From the left-hand menu, select Credentials and click Configure.

  5. Enter the API Key and Client Secret provided by Reality Defender.

  6. Click Save.


Step 5: Activate the Integration

  1. Navigate back to the main Integrations page.

  2. Locate the Reality Defender AudioHook integration and activate it.

  3. Confirm the Status column displays Active.

If the status shows Error: Verify the Connection URI and credentials for accuracy. Contact Reality Defender Customer Success if the issue persists.


Step 6: Test the Integration

  1. In the Architect dashboard, add an Audio Monitoring component at the appropriate point in your call flow β€” typically at the very start.

  2. Place test calls and log in to the Reality Defender web portal for your organization to verify analysis results are appearing.

  3. Use the Reality Defender Session API to retrieve real-time analysis results. Analysis sessions are indexed under the Genesys Conversation ID as the session_id for each call.


Summary

Once all steps are complete, Reality Defender will receive and analyze live caller audio from Genesys Cloud in real time.

If you encounter any issues during setup, please contact Reality Defender Support.

Did this answer your question?