# Method Not Allowed in VideoSDK

**URL:** <https://devforum.zoom.us/t/method-not-allowed-in-videosdk/78717>\
**Category:** Video SDK\
**Tags:** api\
**Created:** [November 13, 2022, 6:15am UTC](https://devforum.zoom.us/t/method-not-allowed-in-videosdk/78717 "2022-11-13T06:15:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bradley.dotnet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bradley.dotnet/32/42955_2.png) [@bradley.dotnet](https://devforum.zoom.us/u/bradley.dotnet)\
**Post date:** [November 16, 2022, 3:07am UTC](https://devforum.zoom.us/t/method-not-allowed-in-videosdk/78717/2 "2022-11-16T03:07:06Z")

</div>

This post ended up having the answer: [Double encoding on UUIDs](https://devforum.zoom.us/t/double-encoding-on-uuids/50695). Apparently the correct approach is to double **URL** encode the session ID. I’m not sure why, since a single encoding should be more than sufficient.

```auto
var safeSessionId = sessionId.Contains('/') ? HttpUtility.UrlEncode(HttpUtility.UrlEncode(sessionId)) : sessionId;

```

Worked for me though. The documentation could use updating to note both the URL encoding, and the fact that it is needed whenever a “/” is present in the session ID

---

_[View the full topic](https://devforum.zoom.us/t/method-not-allowed-in-videosdk/78717)._