Description:
I have successfully implemented the retrieval of call_logs data using the same client_id and secret_id when generating the access token. However, when attempting to retrieve contact_center/queues data, I am encountering an “Invalid access token” error message.
I would like to clarify whether there is a separate or additional scope required to access contact center data through the API.
How To Reproduce:
Create Server-Server OAuth App
Add the following scope:
- View your contact center queue information / contact_center_queue:read:admin
- View all users’ phone information / phone:read:admin
Having this exact same issue on code that was not originally having this issue. We haven’t moved the client_id, client_secret, or anything else into production, so there’s only one machine that’s attempting token requests.
Even stranger, we can hit Zoom Phone endpoints just fine with the exact same access_token, but using the same token for Contact Center yields the exact same issue mentioned here. Invalid access token. Quick python example below demonstrates exactly what is happening for us. The Zoom Phone API call is successful, the Zoom Contact Center call is not with the exact same token that has scopes for (at least per the documentation) both.
I’ve redacted your info since you did not share in the private message. I have opened an inquiry with our API team about the behavior you and others are seeing (ZSEE-122399). I will share updates as they become available.
Thank you for your prompt action and for opening an inquiry with the API team. I appreciate your attention to this matter and look forward to receiving updates as they become available.
My issue was resolved. It seems that we had an administrative issue where the person who had the master account for our ZCC was changed without any of the devs being notified.