I have been using the Historical Queue Performance api for the last month and it has been working fine. I started getting an Unauthorized for url error stating the token does not contain the scope for dataset_queue_performance. I have verified that the scope is selected for the account I am using. All of the other API’s that I am using are still working fine. I have tried removing the scope and adding it back but that did not work. I have also tried creating a new app but I get the same results.
Starting at 11:25 PM on 3/14/2026 I started getting the following error message on every call.
{
“code”: 124,
“message”: “Invalid access token, does not contain scopes:[contact_center:read:dataset_queue_performance:admin].”
}
How I reproduce:
Using Postman, I get an access token for our account requesting a Bearer Token. Then I use the token to access contact_center/analytics/dataset/historical/queue_performance?from=2026-03-02T11:00:00Z&to=2026-03-05T10:59:59Z&page_size=100
It returns the error:
{
“code”: 124,
“message”: “Invalid access token, does not contain scopes:[contact_center:read:dataset_queue_performance:admin].”
}
I began experiencing this same problem this weekend as well.
I validated the scope was selected.
I validated my user permissions have not changed.
I rotated the keys
I removed and re-added the app.
I created a new app with ONLY this scope.
When you log in, you get a JSON response that includes a list of scopes. Our app now returns all other scopes but dataset_queue_performance. The app that only has this permission does not return any scopes.
Hi @Kirk2
Sorry for the late reply here and thanks @Steve13 for sharing your findings too!
I am happy to look further into this
Could you please get a new access token and then access contact_center/analytics/dataset/historical/queue_performance?from=2026-03-02T11:00:00Z&to=2026-03-05T10:59:59Z&page_size=100
if you get the following error
{
“code”: 124,
“message”: “Invalid access token, does not contain scopes:[contact_center:read:dataset_queue_performance:admin].”
}
Can you please share the tracking ID that you get found in the response headers ( x-zm-trackingid )
I will also need your account ID please