Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 20 days ago

    Hi everyone,

    I'm looking for some guidance on a Genesys Cloud integration question.

    We have a third‑party system that updates prompts in our environment by sending data to Genesys through an API. Our call flows then play the updated audio messages based on what they send.

    What we're trying to figure out is whether Genesys provides any way to view or capture the full payload that the third‑party system sends to us. Essentially, we want to confirm exactly what data they're pushing into Genesys when they update the prompt.

    Has anyone worked with this type of setup before? Is there a method-logs, API tracing, event monitoring, or anything similar-that would allow us to see the complete incoming payload?

    Any advice or pointers would be appreciated. Thanks in advance!


    #API/Integrations

    ------------------------------
    Harshit Rana
    Systems Analyst
    ------------------------------


  • 2.  RE: Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 18 days ago

    Good Day Harshit

    I have not done this before but not sure if you could perhaps subscribe to the notification API for this to get all the information when updates are made. - https://developer.genesys.cloud/notificationsalerts/notifications/available-topics

    https://developer.genesys.cloud/notificationsalerts/notifications/available-topics#v2-architect-prompts--id-

    I would perhaps recommend to post this on the developer portal as well.

    Regards



    ------------------------------
    Stephan Taljaard
    EMBEDIT s.r.o
    ------------------------------



  • 3.  RE: Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 17 days ago

    I don't believe you'll be able to see the actual API request/response payloads in Genesys Cloud.  The best you'll be able to do is to view the Audit dashboard to recognize when and which prompt was updated by the 3rd party system.  You can also monitor the frequency and count of the API requests being made by the 3rd party using the API Usage dashboard.

    If you want to see the actual API traffic, then you'd like have to have some sort of middleware sitting between the 3rd party and Genesys Cloud that allows for sniffing the HTTP requests happening between the two systems.



    ------------------------------
    Jim Crespino
    Senior Director, Developer Evangelism
    Genesys
    https://developer.genesys.com
    ------------------------------



  • 4.  RE: Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 17 days ago

    Hi Jim,

    Thanks for the clarification. Yes, I've already tried several approaches on my end, but unfortunately none of them give me access to the actual request/response payloads. For what I'm working on, I really do need to see the raw payloads themselves.

    I appreciate your insight and the suggestions-thanks again for taking the time to explain it.



    ------------------------------
    Harshit Rana
    Systems Analyst
    ------------------------------



  • 5.  RE: Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 17 days ago

    Hi Stephan,

    Thank you for sharing your insight. Unfortunately, with notifications I'm not able to view any of the third‑party payload, as they only display the actions related to the prompt.

    appreciate your help.



    ------------------------------
    Harshit Rana
    Systems Analyst
    ------------------------------



  • 6.  RE: Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 16 days ago

    Hello Harshit, 

    1. Is the the 3rd party updating your prompts on a daily/hourly basis, or are they dynamically changing the next prompt in the flow based on previously collected intent input? 
    2. Also, is this an AppFoundry integration or are you sending the intents and slots to the third party via a data action in the flow, then using the response to load the next prompt?

    If you're using data actions, you may be able to log the response to a variable that you can post to participant data, but it will require you to create a new version of each data action with an updated contract schema.  The new contract is required in order to collect the whole response payload assuming the current data action contract is mapping to a particular property or nested property path (i.e., $.entities.promptvalue) to set the subsequent prompt.  



    ------------------------------
    Carlos Albor
    Principal PS Consultant
    ------------------------------



  • 7.  RE: Need Advice: Capturing Third‑Party API Payloads in Genesys Cloud

    Posted 16 days ago

    Hi Carlos,

    Thanks for the detailed questions.

    The third‑party system doesn't update our prompts on a daily or hourly basis. They only make changes when there's an emergency situation or a specific need, so updates happen on an as‑needed basis rather than dynamically for every interaction.

    It's not an AppFoundry integration. We've simply provided the third party with the API details so they can update the prompt whenever a situation arises that requires it.

    Appreciate your help and guidance on this.

    Thanks,

    Harshit



    ------------------------------
    Harshit Rana
    Systems Analyst
    ------------------------------