Do you have scopes added? If you’re an admin creating an admin-level app, you would just see phone:read:ai_call_summary:admin. If not, you should see the other scope. All this provided phone ai summary is enabled on the account.
Yes I should, I also requested a new token after adding the scopes. But the response is still:
{
"code": 104,
"message": "Invalid access token, does not contain scopes:\[phone:read:ai_call_summary, phone:read:ai_call_summary:admin\]."
}
I created a new app and was able to get a new error code
I believe this is what everyone is getting on their responses and its being worked on correct?
Hmm were you assigned permission to your user role? I have a feeling this may be the issue, but I believe you shouldn’t be able to see the scopes if you don’t have the permission assigned at the role level:
Can you check out the following support articles?
Hi Gianni,
Yes, I have the AI companion feature enabled on my user role (admin). I can confirm that all our users have AI Companion turned on for AI Call Summaries:
Scope on Role Management:
Confirmation of AI Summary on for a user:
Response after confirming scope, role management, and AI Companion turned on:
Hi @dashboard-dev the path parameter above does not have your user id or the call summary id. Did you just leave it like that for the sake of the screenshot? Just want to confirm you called the endpoint with your user id and the aiCallSummaryId in place.
Hi @dashboard-dev you should be able to get the summary for yourself (can you confirm this is the case?).
Otherwise, at this time if you’re trying to access other people’s ai call summary, you will run into issues (see below):
We are actively working to push this through with the product team.
Hi @Gianni,
We facing the same issue with when call the API with the s2s APP.
/accounts/${account_id}/phone/user/${userId}/ai_call_summary/${aiCallSummaryId}`
Do you have any ETA for this bug fix on Zoom side?
Hi @Khai it’s not seen as a bug rather a feature update so it up to the product team, but anticipated rollout by q4.
Thanks Gianni for your update