# Zoom LTI Pro double encoding meeting ids

**URL:** <https://devforum.zoom.us/t/zoom-lti-pro-double-encoding-meeting-ids/84306>\
**Category:** App Marketplace\
**Created:** [March 7, 2023, 2:34pm UTC](https://devforum.zoom.us/t/zoom-lti-pro-double-encoding-meeting-ids/84306 "2023-03-07T14:34:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgoh1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cgoh1/32/72973_2.png) [@cgoh1](https://devforum.zoom.us/u/cgoh1)\
**Post date:** [March 7, 2023, 2:34pm UTC](https://devforum.zoom.us/t/zoom-lti-pro-double-encoding-meeting-ids/84306/1 "2023-03-07T14:34:40Z")

</div>

**Description**

We were investigating why Zoom LTI 1.3 meeting reports were coming up blank. We have a ticket opened now, but just wanted to see if others had the same issue.

For meetings that are recurring, the API has to use a UUID.

According to spec: [https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/reportMeetingDetails](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/reportMeetingDetails)

> If you provide a meeting UUID that begins with a `/` character or contains the `//` characters, you **must** [double encode](https://marketplace.zoom.us/docs/api-reference/using-zoom-apis/#meeting-id-and-uuid) the meeting UUID before making an API request.

However, we’re noticing that for

TEST.ZOOM.JHTEST - Recurring Testing  
Meeting ID: 920 0727 4568

it should be sending `https://zoom.us/v2/report/meetings/bi%2FwHAuARKqvBYhZIshGrw%3D%3D`

but it’s sending (according to the call log)

`https://zoom.us/v2/report/meetings/bi%25252FwHAuARKqvBYhZIshGrw%25253D%25253D`

and failing with a “code”: 3001,  
“message”: “Meeting does not exist: bi%2FwHAuARKqvBYhZIshGrw%3D%3D.”

So it may inappropriately double encoding meeting\_id = bi%2FwHAuARKqvBYhZIshGrw%3D%3D

**How To Reproduce**

1. create a recurring meeting via LTI Pro
2. launch and end the meeting
3. wait for the report link to appear
4. click on the report link

Results:

no meeting report

if you check the zoom call logs, you will see an 404 error, and the details would say

```auto
"response": {
"code": 3001,
"message": "Meeting does not exist: bi%2FwHAuARKqvBYhZIshGrw%3D%3D."
},

```

---

<div class="post-metadata">

**Author:** ![cgoh1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cgoh1/32/72973_2.png) [@cgoh1](https://devforum.zoom.us/u/cgoh1)\
**Post date:** [March 13, 2023, 4:20pm UTC](https://devforum.zoom.us/t/zoom-lti-pro-double-encoding-meeting-ids/84306/2 "2023-03-13T16:20:07Z")

</div>

Zoom deployed a fix on Sunday. We confirm recurring meeting reports now return attendee data.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [April 7, 2023, 12:35am UTC](https://devforum.zoom.us/t/zoom-lti-pro-double-encoding-meeting-ids/84306/3 "2023-04-07T00:35:11Z")

</div>

Closed on April 7, 2023, 12:35am UTC

This topic was automatically closed after 30 days. New replies are no longer allowed.
