# GET /v2/meetings/\<meetingId\> returns BadRequest with invalid access token error

**URL:** <https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679>\
**Category:** Meetings\
**Created:** [August 18, 2026, 4:13am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679 "2026-08-18T04:13:24Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![User50](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@User50](https://devforum.zoom.us/u/User50)\
**Post date:** [August 18, 2026, 4:13am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/1 "2026-08-18T04:13:24Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
GET /meetings/{meetingId}

**Description**

GET /v2/meetings/meetingId returns **200: Invalid access token, does not contain permissions:[User:Read]** for 1 of our customer accoutns. We are using a multi-tenant server-to-server app which works for all other tenants. Following scopes are present in the token, user:read:list\_users:admin,  
meeting:read:meeting:admin, dashboard:read:list\_meeting\_participants:admin, dashboard:read:list\_meetings:admin and cloud\_recording:read:list\_recording\_files:admin

**Error?**  
200: Invalid access token, does not contain permissions:[User:Read]

**How To Reproduce**  
_Steps to reproduce the behavior:_  
\*1. Get a list of meetings using GET /v2/metrics/meetings?type=past&from=&to=. This returns a list of meetings along with id, uuid, topic, start\_time, end\_time etc.  
\*2. GET /v2/meetings/meetingId\>to get the details of each meeting. This return http status code **400: Bad Request**. Response body has ErrorCode: **200** and ErrorMessage: **Invalid access token, does not contain permissions:[User:Read]**

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [August 18, 2026, 1:48pm UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/2 "2026-08-18T13:48:46Z")

</div>

@User50 what do you mean by Multi-tenant Server to Server App?

---

<div class="post-metadata">

**Author:** ![User50](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@User50](https://devforum.zoom.us/u/User50)\
**Post date:** [August 19, 2026, 11:09am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/3 "2026-08-19T11:09:24Z")

</div>

@chunsiong.zoom We have an admin-managed OAuth app, [Microsoft 365 Copilot connector](https://marketplace.zoom.us/apps/7CwKiQcbSf6d4jMXk299pA) which our customers can install and call Zoom APIs. When some of our customers call the GET meeting details endpoint , they are getting a 400 - BadRequest failure.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [August 20, 2026, 2:33am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/4 "2026-08-20T02:33:17Z")

</div>

@User50 I’ll PM you for this

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [August 21, 2026, 3:35am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/5 "2026-08-21T03:35:39Z")

</div>

ZSEE-211921 Internal Reference

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [August 21, 2026, 4:03am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/6 "2026-08-21T04:03:21Z")

</div>

@User50 this specific customer who has added the app might not have the correct permission. The reason is probably due to the role configuration in [Zoom.us](http://Zoom.us). Your customer might not have the “view” permission at the account level. Hence even after approving M365 Copilot connector.

Could you request the customer to check if they have this checkbox enabled for the user?

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/8/7809d7ee05d6781689985e742e607ea1486487b8.png)

---

<div class="post-metadata">

**Author:** ![User50](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@User50](https://devforum.zoom.us/u/User50)\
**Post date:** [September 3, 2026, 9:39am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/7 "2026-09-03T09:39:04Z")

</div>

@chunsiong.zoom Our customer shared few tracking IDs for the failed Zoom API requests. Can you look into your logs and get more details on the errors? Let me know if there is any more information that I can get from the customer.

WEB\_007ed670b6122df34111cd1a2e8dd25c  
WEB\_9690acf69b6a01f7e7ce1e4204eaa23e  
WEB\_e0ec5bb337ccae91869919ff8cd78b1a  
WEB\_ebf50cba08d65cf773418b1beb4b359f  
WEB\_0ec9c899bef969a739be6be4bee08aa7  
WEB\_1a23f1391016e19db1b3e3ba19ba264a

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [September 7, 2026, 11:36am UTC](https://devforum.zoom.us/t/get-v2-meetings-meetingid-returns-badrequest-with-invalid-access-token-error/145679/8 "2026-09-07T11:36:00Z")

</div>

@User50 i need more recent tracking ID as these are dated.
