# Meeting SDK bot unable to join meeting, error code "8"

**URL:** <https://devforum.zoom.us/t/meeting-sdk-bot-unable-to-join-meeting-error-code-8/137073>\
**Category:** Windows\
**Created:** [September 4, 2025, 3:48am UTC](https://devforum.zoom.us/t/meeting-sdk-bot-unable-to-join-meeting-error-code-8/137073 "2025-09-04T03:48:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmandeberg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bmandeberg/32/71080_2.png) [@bmandeberg](https://devforum.zoom.us/u/bmandeberg)\
**Post date:** [September 4, 2025, 3:48am UTC](https://devforum.zoom.us/t/meeting-sdk-bot-unable-to-join-meeting-error-code-8/137073/1 "2025-09-04T03:48:47Z")

</div>

**Description**  
I’m building a Windows Meeting SDK bot using the sdk\_demo\_v2 example. All I need is for the bot to receive the meeting number and passcode and then join a meeting, which is working well on our internal accounts as expected in development. Now we are trying to publish the app, and the Zoom tester is unable to have the bot join her meeting. The error code we’re seeing when she tries to use the bot is “8”, which according to the docs might mean “SDK is not authorized before use.”

Our app shouldn’t require any Zoom OAuth, all you need is to enter the Zoom meeting number and passcode in our web app and the bot (hosted on an AWS EC2) will join your meeting.

I understand that the bot should not yet be able to join meetings from external accounts, but that’s a different error code “63” which doesn’t appear to be in the docs. What can I do about this error code “8” and is there some way to allow the bot to join my Zoom tester’s meeting?

Specifically, the Windows Meeting SDK function that is reporting this error is: `CSDKWithoutLoginStartJoinMeetingUIGroup::onMeetingStatusChanged(ZOOM_SDK_NAMESPACE::MeetingStatus status, int iResult)`

In this case we’re seeing a `status` of `ZOOM_SDK_NAMESPACE::MEETING_STATUS_FAILED` with `iResult` of `8`

**Which Windows Meeting SDK version?**  
6.3.1.53943

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [September 4, 2025, 11:32pm UTC](https://devforum.zoom.us/t/meeting-sdk-bot-unable-to-join-meeting-error-code-8/137073/2 "2025-09-04T23:32:36Z")

</div>

Hi @bmandeberg — [Error 8 means “SDK is not authorized before use”](https://developers.zoom.us/docs/meeting-sdk/windows/error-codes/), but if this is a Zoom tester account it usually points to them being logged into the wrong Zoom account. I’ve seen cases where testers try to run the app while signed in with a personal Zoom login instead of the assigned tester account, and the SDK rejects the auth

I’d ask your tester to confirm they’re signed into the correct **Zoom-provided tester account** before retrying. Once they switch to the right account, the join flow should succeed

---

<div class="post-metadata">

**Author:** ![bmandeberg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bmandeberg/32/71080_2.png) [@bmandeberg](https://devforum.zoom.us/u/bmandeberg)\
**Post date:** [October 16, 2025, 3:02am UTC](https://devforum.zoom.us/t/meeting-sdk-bot-unable-to-join-meeting-error-code-8/137073/3 "2025-10-16T03:02:07Z")

</div>

Well, for anyone who may run into this same issue - after all that it turns out that this error code “8” I’m getting from the Zoom SDK was simply from having spaces in the Zoom meeting ID submitted to the Zoom bot. So, I’m not sure if this “8” is actually referring to an SDK auth error in this case.

---

<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:** [October 16, 2026, 3:03am UTC](https://devforum.zoom.us/t/meeting-sdk-bot-unable-to-join-meeting-error-code-8/137073/4 "2026-10-16T03:03:01Z")

</div>

Closed on October 16, 2026, 3:03am UTC

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
