Henry.Zambrano | 2024-02-08 18:41:09 UTC | #1
I'm no longer able to see the list of my voicemail in the Genesys Cloud interface. When I take a look to the browser console I see the following error for POST /api/v2/voicemail/search 403 Forbidden
{
"message": "You are not authorized to access the voicemail message",
"code": "forbidden",
"status": 403,
"contextId": "bf6d9925-b5e1-4499-8f54-3cae35ac29d3",
"details": [],
"errors": []
}
I theory, I should not be receiving that error since I'm searching for my own voicemails. The documentation also indicates that resource has "no permissions required"
tim.smith | 2024-02-08 19:08:55 UTC | #2
You're getting the 403 because the voicemail you're trying to access is owned by a group. If that doesn't tell you what you need to know to make a configuration change on your end to allow access, please open a case with Genesys Cloud Care to troubleshoot further. We don't have access to your org's data via the forum and can't discuss your private configuration in this public setting. I can only see the nature of the error, not specifically what configuration is causing it and therefore can't suggest what to change to fix it.
Henry.Zambrano | 2024-02-08 22:57:58 UTC | #4
Thank you Tim, you are right. After further research, I realized that indeed I'm trying to access to a VM owned by a group to which I no longer belonged. However, I would expect that the fact that I no longer belong to that group doesn't block the display of the other messages that I have, including my user voicemail or voicemails of other groups where I'm still a member. As soon as I put back my user as member of that group, I was able to see my VMs (all of them, including personal/user VMs). Thanks again for your prompt response.
tim.smith | 2024-02-08 23:14:57 UTC | #5
Henry.Zambrano, post:4, topic:24554
I would expect that the fact that I no longer belong to that group doesn't block the display of the other messages that I have, including my user voicemail or voicemails of other groups where I'm still a member.
Yeah, that doesn't seem right. It's a search endpoint, so it would make sense that the results simply wouldn't contain voicemails you don't have access to. If you didn't explicitly request something you don't have access to in the query, that's probably worth reporting to Care. If you did explicitly include that group (or something like that) on the query, a 403 does make sense because you can't have what you asked for.
system | 2024-03-09 23:15:57 UTC | #6
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 24554