I would like users to be able to activate call forwarding of the queue on their mobile when they are on call the night. For now I have the impression that we had to go through Webex App Hub as admin to do this. I would like my users to be autonomous. So is there a way? and if the only way is to go through an API Integration, how to do it (because I really don't know anything about it)?
Thanks in advance,
If this is in regards to handling forwarding for a Webex Calling queue then only an admin can do it. There is an API for updating it but it requires an access token that belongs to an admin. See: https://developer.webex.com/docs/api/v1/webex-calling-organization-settings-with-group-call-management-features/update-call-forwarding-settings-for-a-call-queue
If this is in regards for queues in Webex Contact Center then that is handled by a different team, the following link shows how you can get support Webex Contact Center APIs. See: https://community.cisco.com/t5/contact-center/webex-contact-center-apis-developer-community-and-support/td-p/4558270
Yes it's about "to handling forwarding for a Webex Calling queue". Your link doesn't work but I think you mean this link : https://developer.webex.com/docs/api/v1/webex-calling-organization-settings/update-call-forwarding-settings-for-a-call-queue . Unfortunately that's what I thought, a user can't transfer the call to his phone on his own :'(
Not if you use an integration to generate your access token. You can authorize with an integration one time to get your initial access token and your refresh token and then going forward use the refresh token to programmatically generate new access tokens. The access token generated by an integration is valid for 14 days and the refresh token for 90 days. However, each time the refresh token is used to generate a new access token the expiry timer on the refresh token is reset back to 90 days so if you're using the refresh token once ever 14 days to generate a new access token then the refresh token will never expire and you'll never have to manually go through the OAuth flow again.