Genesys Cloud - Main

Has anyone had a customer that needs to monitor mailbox activity to ensure users are managing their mailboxes?  The API's provided by Genesys worked well for this
Specifically /api/v2/voicemail/users/{userId}/mailbox allowed an OAuth user to collect data about a mailbox and use this for reporting as needed.

Alas Genesys have not maintained this flexibility with /api/v2/voicemail/groups/{groupId}/mailbox

Despite very little in the documentation showing this change it appears you must be a user (not an Oauth client) AND a member of the Group in order for this api (and the similar /messages one) to return successfully.

Does anyone think this is intentional - i.e. should I raise a bug - or has you found other ways to help your customer monitor mailbox activity or is this a unique requirement nobody else in the Genesys customer base has every asked for?

Hi Paul,

I have not worked on this specific use case myself, but from my understanding based on the related community threads I found, this looks more likely to be intentional than a bug.

In particular, there is a response in the thread below indicating that the group voicemail API works only with authentication that has a user context associated with it, which seems consistent with what you are seeing:
https://community.genesys.com/discussion/group-voicemail-unread-count-from-api

I also found this related thread, which may be useful for additional context:
https://community.genesys.com/discussion/count-of-unread-voice-mails-in-a-voice-mail-group

So based on that, I would lean more toward this being a by-design user-context restriction rather than a bug, though it still feels like a valid enhancement request if the customer needs central monitoring/reporting for group voicemail activity.

Would be interested to hear if anyone has found a better workaround for this use case.

Has anyone had a customer that needs to monitor mailbox activity to ensure users are managing their mailboxes?  The API's provided by Genesys worked well for this
Specifically /api/v2/voicemail/users/{userId}/mailbox allowed an OAuth user to collect data about a mailbox and use this for reporting as needed.

Alas Genesys have not maintained this flexibility with /api/v2/voicemail/groups/{groupId}/mailbox

Despite very little in the documentation showing this change it appears you must be a user (not an Oauth client) AND a member of the Group in order for this api (and the similar /messages one) to return successfully.

Does anyone think this is intentional - i.e. should I raise a bug - or has you found other ways to help your customer monitor mailbox activity or is this a unique requirement nobody else in the Genesys customer base has every asked for?