# Meeting\_summary {"code":200,"message":"No permission."} in Admin-Managed app

**URL:** <https://devforum.zoom.us/t/meeting-summary-code-200-message-no-permission-in-admin-managed-app/129329>\
**Category:** Meetings\
**Created:** [March 6, 2025, 11:18am UTC](https://devforum.zoom.us/t/meeting-summary-code-200-message-no-permission-in-admin-managed-app/129329 "2025-03-06T11:18:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hemsharm](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hemsharm/32/60967_2.png) [@hemsharm](https://devforum.zoom.us/u/hemsharm)\
**Post date:** [March 6, 2025, 11:18am UTC](https://devforum.zoom.us/t/meeting-summary-code-200-message-no-permission-in-admin-managed-app/129329/1 "2025-03-06T11:18:18Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
[https://api.zoom.us//v2/meetings/thr/dsg6AjaWjZRPzFxWww==/meeting\_summary](https://api.zoom.us//v2/meetings/thr/dsg6AjaWjZRPzFxWww==/meeting_summary)

**Description**  
The meeting summary API should return summary but instead retuning {“code”:200,“message”:“No permission.”} . I am using admin-managed app. and having meeting:read:summary:admin and meeting:read:list\_summaries:admin added to scopes

**Error?**  
{“code”:200,“message”:“No permission.”}

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 7, 2025, 6:45pm UTC](https://devforum.zoom.us/t/meeting-summary-code-200-message-no-permission-in-admin-managed-app/129329/2 "2025-03-07T18:45:54Z")

</div>

Hi @hemsharm  
Thanks for reaching out to us!  
This endpoint you shared: [https://api.zoom.us//v2/meetings/thr/dsg6AjaWjZRPzFxWww==/meeting\_summary](https://api.zoom.us//v2/meetings/thr/dsg6AjaWjZRPzFxWww==/meeting_summary) has typo, it has an extra “/” before ‘v2’. Can you please fix it and try again?

If you are querying with the meeting UUID, you should double-encode it before making the request, because the “/” can be affecting your request