Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Adding division to OAuth to restrict value return from API

    Posted yesterday

    Hi All,

    We have added couple of division in Client Oauth to get only values that are part of those division

    Here is the api we are using  to fetch the deleted conversation Ids.

    POST  /api/v2/audits/query

               body: JSON.stringify({
                    interval,
                    serviceName: 'Quality',
                    filters: [
                        { property: 'EntityType', value: 'Recording' },
                        { property: 'Action', value: 'Delete' }
                    ]
                })
    /api/v2/audits/query/${transactionId}
    However I see we are getting conversationIds from other division as well.
    Anyone has this knowledge?


    #Integrations

    ------------------------------
    Riddhi S.
    .
    ------------------------------


  • 2.  RE: Adding division to OAuth to restrict value return from API

    Posted yesterday

    Hi Riddhi,

    I did some digging on this. I can see that Genesys recommends the asynchronous Audit API with Service = Quality, EntityType = Recording and Action = Delete for retrieving recording deletion events.

    However, I couldn't find anything confirming that these audit results are automatically filtered by the divisions assigned to the OAuth client.

    There are also previous examples where users of /api/v2/audits/query mention performing additional filtering on the returned results.

    https://community.genesys.com/discussion/recording-audit-by-user

    https://community.genesys.com/discussion/view-audit-trail-for-deleted-recordings

    Hopefully someone from Genesys can confirm whether Quality/Recording audit events are division-aware, or whether the conversation IDs need to be filtered separately after retrieving the audit results



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------