Thanks Bronze. I'd visited that page but hadn't seen the information you provided.
FYI I ended up raising a case with Customer Care and so I've provided your information to them. Hopefully they will update API Explorer to include this info?
Original Message:
Sent: 06-10-2025 08:27
From: Bronze Cooley
Subject: GET /api/v2/users/{userId}/callforwarding 403 response
I can appreciate the PTSDs of Customer Care. The user that you are trying to pull information for needs to have the following permissions:
https://help.mypurecloud.com/articles/forward-incoming-calls/
- Conversation > Call Forwarding > Edit
- Conversation > Call > Add
- Conversation > Conference > Add
- Voicemail > Voicemail > Receive
This is presuming your 403 is:
The request failed with response code: 403. Message: The user is not permitted to use call forwarding
------------------------------
Bronze Cooley
Principal Engineer, Client Service Desk • US-PUBLIC SECTOR
github
Demo Page
Original Message:
Sent: 06-09-2025 16:58
From: Nick Tait
Subject: GET /api/v2/users/{userId}/callforwarding 403 response
Thanks Jason. Based on previous experience with Customer Care and documentation-related issues, I'll first try reporting this as a bug on the Platform API page.
------------------------------
Nick Tait
Genesys Consultant
Original Message:
Sent: 06-09-2025 08:54
From: Jason Mathison
Subject: GET /api/v2/users/{userId}/callforwarding 403 response
I would suggest opening a support ticket to investigate if that is the proper behavior, and if so, update the documenation.
------------------------------
--Jason
Original Message:
Sent: 06-08-2025 21:18
From: Nick Tait
Subject: GET /api/v2/users/{userId}/callforwarding 403 response
Hi there.
The GET /api/v2/users/{userId}/callforwarding API is documented as requiring no permissions, and scope of either users or users:readonly. But what I'm finding is that if the user being queried doesn't hold conversation:callForwarding:edit permission, the API returns a 403 Forbidden response.
Unfortunately I can't find any documentation to explain this behaviour, and so I'm questioning whether this is correct or not?
Can anyone point me in the direction of any documentation to explain this behaviour?
Thanks,
Nick.
#PlatformAPI
------------------------------
Nick Tait
Genesys Consultant
------------------------------