No idea why this is happening, our appfoundry integration throws a 401 unauthorized when initiating webrtc calls via the platform api. we are using multi-org oauth tokens that work for other endpoints, but the /api/v2/communications/outbound/calls endpoint rejects the auth. the access token is valid for the correct org. are there specific scopes missing for webrtc signaling in a multi-tenant setup?
You need to verify the OAuth client permissions in the integration settings. The Performance dashboard relies on specific scope grants that may not be automatically inherited for WebRTC signaling in multi-tenant environments.
Review the “Communications” section under the application’s API access configuration. Ensure the outbound call scope is explicitly enabled for the target organization, as the default token often lacks this privilege.
Have you tried explicitly adding the communications:outbound:write scope?
are there specific scopes missing for webrtc signaling in a multi-tenant setup?
Zendesk doesn’t handle OAuth scopes this granularly, so it is easy to miss this requirement during migration.