# New Features not in latest version of the API (version 11)

**URL:** <https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525>\
**Category:** API and Webhooks\
**Created:** [January 9, 2018, 7:58pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525 "2018-01-09T19:58:24Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [January 9, 2018, 7:58pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/1 "2018-01-09T19:58:24Z")

</div>

The following features are minimally viable for a full working ZRC to allow integrators to fully utilize a close enough representation of the zoom room controller.&nbsp; I wont be releasing anything on my end until all of these features are scoped out in a stable release on both windows and mac clients.

&nbsp;

Feature #1: Sharing-only meetings: share laptop and iPhone/iPad/Mac, for a specific duration feature.

&nbsp;

Feature #1 Description:&nbsp; In the iPad app, there is a sharing tab.&nbsp; When a user clicks it a new meeting ID is given to the iPad app so that they might start sharing and know the meeting ID.&nbsp; In the ZRC API, we do not have this ability to start a share and get a meeting ID returned back to us.&nbsp; It should be a new zEvent when the sharing meeting is live and we have a number to show to the user.&nbsp; It should possibly have a status of 1 like when you are starting a meeting that it is loading the meeting ID.

&nbsp;

Feature #2 Title:&nbsp; Share content in a meeting: laptop and iPhone/iPad/Mac, sharing key, sharing URL, sharing meeting ID

&nbsp;

Feature #2 Description: Currently there is a read only screen that shows on the iPad airplay screen that shows the sharing url the meeting ID and the sharing key.&nbsp; I want to expose a way when asking about a meeting or a “sharing only meeting” that we have the sharing key shown in the iPad.

&nbsp;

Feature #3 Title:&nbsp; Claim host: we also may need to accept a claim host key.

Feature #3 Description: If you are not the host in the meeting, we need the ability to claim the host using the claim host key to submit the host key via the number a user enters.

&nbsp;

Feature #4 Title:&nbsp; Add video recording start/stop

Feature #4 Description: Currently the ZRC does not provide facilities to initially enter an email address when the user clicks start recording.&nbsp; We need to know first off whether the meeting is automatically having recording ON/OFF, where is this information stored so that we can know whether the meeting already has an email address to send to and we don’t have to ask for one.&nbsp; If the meeting is not being recorded and we don’t have an email address, we will prompt for an email address and then pass that to the ZRC for recording emails.&nbsp; Later after the initial one is recording, the user has the ability to stop the recording so we need a stop recording feature to notify of a clipped video to clip.&nbsp; Then the user can start recording again if we already have sent an email to the ZRC.

&nbsp;

Feature #5 Title:&nbsp; Windows preview build is still not available to test

Feature #5 Description: Alex still has not been able to get a non-wire shark build going so we can preview the windows build of zoom rooms SSH client.&nbsp; He needs something done on the core app build so that 3rd party developers can be able to interface with the SSH client without a long drawn out wire-shark process.

&nbsp;&nbsp;

Feature #6 Title: Pan/Zoom/Tilt is not supported for the hosts Camera

Feature #6 Description:&nbsp; We don’t need presets for v1 release, but we need basic abilities to fire pan zoom and tilt requests to supported cameras.

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [January 12, 2018, 1:05pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/2 "2018-01-12T13:05:03Z")

</div>

Feature #7 and 8: For a participant we should allow a “Make Host” ability and “Remove”.&nbsp; These are bare minimum features I feel users will accept.&nbsp; The rest of the context menu on participants when in a meeting can wait for a future version.

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [March 13, 2018, 2:09pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/3 "2018-03-13T14:09:11Z")

</div>

Scott, getting any closer on any of these items and new features?&nbsp; I would love to experiment with any alpha or beta features to see how they hold the test of “Dave testing”

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [March 13, 2018, 2:13pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/4 "2018-03-13T14:13:36Z")

</div>

I am having to implement PZT macros in place of the lacking of camera control myself and i will just allow the integrator control that way until your solution is in place to call the functions themselves.&nbsp; I really think the best way for pan and zoom and tilt would be that we send you a startPan and endPan request and keep panning zooming or tilting until we end it.&nbsp; Or possibly unit test some really fast ssh command events where things pan/zoom or tilt quickly and smoothly.

---

<div class="post-metadata">

**Author:** ![Scott\_Firestone](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/scott_firestone/32/568_2.png) [@Scott\_Firestone](https://devforum.zoom.us/u/Scott_Firestone)\
**Post date:** [March 13, 2018, 5:32pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/5 "2018-03-13T17:32:47Z")

</div>

Dave: We are progressing very slowly on these features. I have no firm dates for when these are going to be available.

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [March 13, 2018, 6:58pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/6 "2018-03-13T18:58:04Z")

</div>

Yea just let me know if you get 1 done I can test on a beta and implement callers to your functions.&nbsp; Thank you.

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [May 3, 2018, 8:26pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/7 "2018-05-03T20:26:20Z")

</div>

We also need to be able to remove a participant in a meeting

---

<div class="post-metadata">

**Author:** ![Scott\_Firestone](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/scott_firestone/32/568_2.png) [@Scott\_Firestone](https://devforum.zoom.us/u/Scott_Firestone)\
**Post date:** [May 3, 2018, 8:57pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/8 "2018-05-03T20:57:07Z")

</div>

Yes: These additional items will be in 1.1 because they are easy to implement:

- Remove a participant in a meeting (Expel)
- Test microphone
- Test Speaker
- Lock meeting
- Windows build connection bug fix.

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [May 10, 2018, 5:25pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/9 "2018-05-10T17:25:58Z")

</div>

Feature #9:&nbsp; We had talked about this originally, but I forgot to append it here.&nbsp; We need various support for toggling the different monitor view features shown in the middle row on the left side where you can switch positions of a few things and how you want your meeting displays to show things.

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [May 16, 2018, 7:41pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/10 "2018-05-16T19:41:04Z")

</div>

Feature #10 - Currently there is no way to join a meeting from the SSH client by using a password in a meeting.&nbsp; Maybe when you join, a password response error should be responded with so we can show something in the UI to enter a password

---

<div class="post-metadata">

**Author:** ![Atlona\_Velocity](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/atlona_velocity/32/1021_2.png) [@Atlona\_Velocity](https://devforum.zoom.us/u/Atlona_Velocity)\
**Post date:** [June 25, 2018, 2:48pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/11 "2018-06-25T14:48:20Z")

</div>

Feature #12: Discrete mute capabilities for MUTE ON/MUTE OFF for the audio output.&nbsp; I would have thought these would be in there, but maybe I missed them in the API.&nbsp; It’s not ideal for us to keep track of a mute state and send zero or the previous mute levels.

---

<div class="post-metadata">

**Author:** ![John\_Calvert](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@John\_Calvert](https://devforum.zoom.us/u/John_Calvert)\
**Post date:** [July 2, 2018, 11:13pm UTC](https://devforum.zoom.us/t/new-features-not-in-latest-version-of-the-api-version-11/525/12 "2018-07-02T23:13:48Z")

</div>

For&nbsp;Feature #12:&nbsp;For audio output devices, there is no mute/unmute; instead, you set the volume to zero for that device.

However, it is true that the API uses “Windowing”. There is a separate volume level per audio output device, and when you switch to a new output device, the output volume switches to the volume level for that output. You’ll get a notification if the volume changes as a result of switching to a new audio output device.
