I have successfully configured and activated the S2S OAuth app and can authenticate successfully. The app is able to obtain access tokens and access other Zoom APIs such as /v2/users and Zoom Contact Center APIs.
Evidence
The token currently contains these scopes:
Plain Text
user:read:list_users:admin
contact_center:read:agent_report:admin
contact_center:read:list_queues:admin
contact_center:read:agent_status_report:admin
contact_center:read:dataset_outbound_dialer_performance:admin
contact_center:read:dataset_agent_performance:admin
contact_center:read:dataset_flow_performance:admin
contact_center:read:call_journey_log:admin
contact_center:read:queue_report:admin
contact_center:read:dataset_disposition:admin
contact_center:read:dataset_expert_assist:admin
zoom_quality_management:write:interactions:admin
Quality Management is enabled
I have access to the Quality Management UI and can view interaction reports at:
Plain Text
/iq/qm/interactions/all
which indicates that Quality Management is available in our tenant.
API test results
When calling:
HTTP
GET /v2/qm/interactions
Zoom returns:
JSON
{
“code”: 104,
“message”: “Invalid access token, does not contain scopes:[zoom_quality_management:read:interactions,zoom_quality_management:read:interactions:admin]”
}
When calling:
HTTP
GET /v2/qm/calibrations
Zoom returns:
JSON
{
“code”: 104,
“message”: “Invalid access token, does not contain scopes:[zoom_quality_management:read:calibrations,zoom_quality_management:read:calibrations:admin]”
}
Problem
The required scopes reported by the API are not available in the Server-to-Server OAuth scope picker.
I can see:
Plain Text
zoom_quality_management:write:interactions:admin
but I cannot find:
Plain Text
zoom_quality_management:read:interactions
zoom_quality_management:read:interactions:admin
zoom_quality_management:read:calibrations
zoom_quality_management:read:calibrations:admin
Request
Could you please confirm:
Whether these Quality Management read scopes should be available for my account.
Whether additional licensing, permissions, or feature enablement is required.
Whether there is a tenant-side entitlement issue preventing these scopes from appearing in the Server-to-Server OAuth application.