Zoom URL Schemes

Tim Slagle
Nov 6, 2017 · 2 min read

Deprecated: Client URL Schemes

External support for direct client URLs has been removed. For any questions, pleases contact developersupport@zoom.us.

Let’s take a quick look at the URL schemes that we expose today — we get frequent questions on this topic.

By default, it’s your responsibility as the app developer to let your users download and install the client package from zoom.us. Or you can distribute the client page by your channel.

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

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

Protocol Examples

Joining A Meeting

Windows/Mac client: zoommtg://zoom.us/join?confno=123456789&pwd=xxxx&zc=0&browser=chrome&uname=Betty

iOS/Android Client: zoomus://zoom.us/join?confno=123456789&pwd=xxxx&zc=0&browser=chrome&uname=Betty

Starting A Meeting

Windows/Mac client: zoommtg://zoom.us/start?browser=chrome&confno=123456789&zc=0&stype=100&sid=lBGPGzGdT8–2Yf3kjDY5gg&uid=lBGPGzGdT8–2Yf3kjDY5gg&token=xxxxxx&uname=Betty

iOS/Android client: zoomus://zoom.us/start?browser=chrome&confno=123456789&zc=0&stype=100&sid=lBGPGzGdT8–2Yf3kjDY5gg&uid=lBGPGzGdT8–2Yf3kjDY5gg&token=xxxxxx&uname=Betty

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 the user GET REST API call)
  • pwd: Meeting Password

Hope this helps and please do use our forums if you have follow up questions.