Question
People commonly ask on the Zoom Developer Forum:
Why does the Meeting SDK headless Linux sample only join meetings when the bot and the meeting organizer are on the same Zoom account, but fail to join meetings created by a different user? Additionally, what steps can I take to resolve issues like meetingFailed code 63 when trying to join meetings hosted by other Zoom accounts?
Answer
The primary reason for the issues encountered when trying to join meetings hosted by different Zoom accounts is that the Meeting SDK app is not published. An unpublished Meeting SDK app is restricted to joining meetings that belong to users within the same Zoom account as the app’s credentials. This limitation leads to failures, such as meetingFailed code 63, when attempting to join meetings hosted by users on other Zoom accounts.
To resolve these issues, follow these steps:
-
Verify App Status: Check if your Meeting SDK app is published. If it is unpublished, it will only be able to join meetings within the same Zoom account.
-
Publish Your App: If you need the bot to join meetings hosted by other Zoom accounts, you must publish your Meeting SDK app. You can choose to publish it as an unlisted app if you do not want it to be publicly listed.
-
Testing Before Publishing: For initial testing, ensure that the meetings are hosted by users within the same Zoom account as the Meeting SDK credentials. This will allow you to confirm that the bot is functioning correctly before moving on to external meetings.
-
Post-Publication Testing: Once your app is published and approved, you can test joining meetings hosted by other accounts using their invitation links.
By following these steps, you should be able to resolve the account permission issues and successfully join meetings hosted by other Zoom accounts.
Zoom Developer Forum Examples
Some examples of this question are:
