Client Installation Follow

Update: Please see our Developer Portal for more up to date content on our REST API and Mobile SDK.

By default, it’s your responsibility to let your user download and install the client package from Or you can distribute the client page by your channel.

If a user doesn’t install client pre starting or joining a meeting, you should be aware that a pop up browser windows which detects your current installation and decide to install or update client on your machine.


If all of your users have installed, you can use the “zoomus:” protocol instead of “https:” to start application. The benefit of zoomus protocol is that your users will not be brought to another page to start or join a meeting.

Typical zoomus and zoommtg protocol examples:

Joining A Meeting

Windows/Mac client: zoommtg://

iOS/Android Client: zoomus://

Starting A Meeting

Windows/Mac client: zoommtg://

iOS/Android client: zoomus://

Parameters in zoomus and zoommtg protocol:

  • confno: Meeting ID
  • zc: Zoom meeting control options
    • 0 - with video and audio
    • 1 - screen share only without video and audio
  • browser: browser type (optional)
    • "chrome"
    • "firefox"
    • "msie"
    • "safari"
  • uname: User name
  • stype: User's login type
    • 100 - Work Email user
    • 0 - Facebook user
    • 1 - Google user
    • 101 - SSO user
    • 99 - Cust API user
  • uid: Host user ID
  • token: Host user token, does not until user change the password (You can get it from user/get REST API call)
  • pwd: Meeting Password
Was this article helpful?
Have more questions? Submit a request
Powered by Zendesk