Good afternoon @gianni.zoom, just following up on this one in case there were anu updates
Hi @joeyharrington @kslowpes , engineering just confirmed the following: Zoom Phone Admin Portal/Account Owner can’t see the end user’s call summary in the web UI and currently, the API has the same logic. I asked if there are plans to expand this already on the roadmap and if not, to create a feature request for account owners/admin to get call summaries of other users.
2 Likes
Thank you @Gianni. I had submitted it as a feature request back in April 3rd (FR-13627). On April 30th, I received a response that it was already satisfied with the "GET /phone/user/{userId}/ai_call_summary/{aiCallSummaryId} " (which wasn’t yet available when I first requested). So I am glad to see at least a confirmation of this disconnect of the info.
Even the having to come here to discuss this came from trying to put in a ticket and having them automatically closed stating that it was clearly a “configuration issue”
So, if you do receive a response from them regarding it being on the roadmap or not, please give us an update.
Thank you!!
1 Like
Hi @gianni.zoom ,
I was following the previous thread as we awaited the general availability of Call Summaries. Much like other users and common use cases, the goal is to bring call summaries back into CRM. However, we are getting the same error with S2S implementation of 403 “You do not have permission.” This is a bummer as we have clients who are desiring this capability be deployed to their systems. Do we have an anticipated date to completion because as of now, we can assume getting AI Summaries is still not generally available despite the public release of the endpoint on 4/15.
Per usual, thanks for your feedack and have a blessed day ahead.
x-zm-trackingid": [“PBX_SERVER_0684879e927a71786ed”]
1 Like
Just joining the discussion to confirm I am having the same issue after spending several hours trying to get past the permission error before checking online and finding this thread, LOL. Any update on a possible solution? Thanks
2 Likes
Hi @kslowpes @positive.results @IT110 ,
Thank you for your feedback! I am inquiring again with the product team about addressing this feature for implementation. I just sent them a detailed message again today.
As of right now, what we’re currently seeing is expected behavior as I shared here:
I agree, however, that one would expect the same sort of privilege access to be consistent with other areas of our platform. For example, the way Admin can query for the meeting cloud recordings or transcripts of other users with certain admin scopes. For this reason, I thought the call summary behavior was a bug as well!
I’ll be monitoring the progress of this closely.
1 Like
Hey @gianni.zoom,
The below
is only referring to the admin scope, not the master scope right?
(i.e. the master scope issue is an actual bug and not “expected behaviour”).
Slightly confused since you tagged IT110 when they haven’t specified which scope they’re using.
To recap, for me, the error message states that
Invalid access token, does not contain scopes:[phone:read:ai_call_summary:master]
despite the phone:read:ai_call_summary:master being explicitly assigned in my application.
Feature request (ZSEE-172174) in request.
Tagged him because I’m replying all to you. This is expected behavior if you’re trying to access call summaries from other users accounts however it’s not intuitive as I was sharing in my previous response @tamn
Hi @gianni.zoom,
I don’t understand how it can be “expected behaviour” if the error message (stating that master scope is required) completely contradicts reality (I’ve already granted the master scope).
At minimum, the error message for master scope is incorrect.
This is akin to showing a security guard your ticket at a concert and they respond with “you need a ticket to enter”.
Hi @tamn ,
I do not disagree with you which is why I submitted the feature request. I was surprised too. As of now, you can only retrieve your own ai call summaries via API regardless of scope.
Please re-read here:
If I’ve misunderstood you and you mean to communicate that you cannot receive your own call summary, I am happy to receive a fresh zm-tracking-id and push on the matter further.
@gianni.zoom again, my point is simply that it cannot be “Expected Behaviour” (warranting a feature request), but rather a bug (requiring a fix).
You cannot have the error
{
"code": 104,
"message": "Invalid access token, does not contain scopes: [phone:read:ai_call_summary:master]."
}
when, as per OP’s post, they have already granted it.
Whether it’s possible as a capability or not, Web or API, doesn’t matter. It doesn’t change the fact that the current error message contradicts reality and requires a fix.
If the “expected behaviour” is that this isn’t supported, it should instead error with “Cannot view another user’s ai summary”, not about missing scope. The current message is simply miscommunication.
1 Like
Hi @tamn , I agree the error message is misleading and just made sure to double back and confirm that engineering:
-
Fix the error code:
-
Follow through to ensure
phone:read:ai_call_summary:adminandphone:read:ai_call_summary:masterallow users with proper permissions to query summaries of users other than themselves (feature request).
Can you please confirm if you’re able to fetch your own summary?
Thank you @gianni.zoom.
As for
Can you please confirm if you’re able to fetch your own summary?
I only use an admin/master account that manages other employees, so I don’t have my own calls/summaries.
However, this has already been confirmed by Joey from above:
Hi @tamn I know it was confirmed for Joey. It’s helpful to have another data point since we are confirming the current behavior across different users/accounts for the same endpoint(s).
+1 here for this same issue of being unable to access AI call summaries of users in my organisation despite using an admin account and enabling both admin and master scopes.
Spent several hours banging my head against the [403] You do not have permission error before finally ending up here. Creating a new forum account just to be notified of updates on this issue.
The AI Call Summary API endpoint is pointless if we can’t even use it to access org data as an admin, really need this fixed!
2 Likes
Hi,
I’m experiencing the same issues as listed above. Both phone:read:ai_call_summary:admin & phone:read:ai_call_summary:master scopes are enabled, but I can only access my call summaries. If the only option is to create S2S accounts for each of my users in the organization, and make several API calls for only AI call summaries, so be it. However, I’d like to know if this bug plans to be fixed in the near future so I don’t waste time working around it.
Also, I attended the Zoom SDK and API - Developer Office Hours two weeks ago, but it seemed as if they were not aware of the issue. They assumed that the :master call would be sufficient, but my experience and the posts above suggest otherwise. I plan to attend today’s session and see if they offer any updates.
Hi
I’m having the exact same issue and this should be considered as a bug rather than feature request. Any update on this?
Hi @Reverest I am working urgently on this to get the team to make this change. Thank you for your feedback.
We have a same issue.
/phone/user/{userId}/ai_call_summary/{aiCallSummaryId}
x-zm-trackingid: WEB_e44067e7eec192309ab6e8e0449420de
{“code”:403,“message”:“You do not have permission.”}
This is mission critical for us right now. Please fix it.
Hi
Zoom Devs,
I’m working with the AI Call Summary Detail endpoint (GET /phone/user/{userId}/ai_call_summary/{aiCallSummaryId}), and I’ve run into an issue that seems different from what others have reported.
While most users are receiving a 400 error when scopes are misconfigured, I’m consistently getting the following code 104 response:
{
"code": 104,
"message": "Invalid access token, does not contain scopes:[phone:read:ai_call_summary, phone:read:ai_call_summary:admin]."
}
1 Like