Alan,
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.
Note, if you are building on AWS, then our Amazon Event Bridge integration might be an even better event mechanism for you to look into.
Lastly, these kinds of questions are probably best asked in our Developer Center Forum at https://developer.genesys.cloud/forum.
I hope that helps.
------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com------------------------------
Original Message:
Sent: 03-14-2023 09:08
From: Alan Klein
Subject: Genesys Audiohook Monitor and pushing arbitrary Key:Value pairs to server
Is there a way to push metadata from Genesys to the Audiohook Monitor server via key:value pairs? I don't see anything explicitly call this capability out but wanted to see what the communities experience has been here.
It seems the server can send metadata back to the client (Genesys) but not the other way around?
The server may send "event" messages at any time after the connection has been successfully opened. Events allow the server to send metadata and other notifications to the client (Genesys). The parameters property of the "event" message contains an entity object implemented as tagged union of typed (meta)data.
#ArchitectureandDesign
#Integrations
------------------------------
Alan Klein
Cresta Intelligence
------------------------------