Passing Additional Metadata to the Notifications API

What is the suggested way to add additional call metadata when integrating with Audiohook Monitor and the Notifications API. Reference the JSON object referred to below.

What steps do we have our customers follow to add additional key:value pairs we can consume?

From a previous question answered by Genesys on this topic, I was provided this part:

In a typical Audiohook integration you'll be a websocket server that will receive the Audiohook streams, but you'll most likely also need to maintain a websocket back into Genesys that is connected to our Notification API and subscribed to topics. When you receive the "Open" event from the Audiohook Monitor, if you accept that then you should probably also subscribe to events for the conversation via the Notification API. That will allow you to have access to the entire Conversation JSON object, including participant attribute key/value pairs. You can then use other Genesys Cloud APIs as needed to work with that interaction.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.