Patch account options from master (On-Premise) - Need documentation

API and Webhooks
21

Hey @bo.staahle,

This will be fixed in a release this weekend. Here is the JSON schema:

{
"share_mc": true,
"meeting_connector_list": ["127.0.0.1","127.1.1.0"],
"share_rc": true,
"room_connector_list": ["127.0.0.1","127.1.1.0"]
}

Thanks,
Tommy

22

Hi Tommy,

Not working - for me it just selects all Meeting Connectors, like the list is being ignored.
New syntax and data type is not working for the Room Connectors either.

Old Syntax is still working for the Room Connectors. Not for Meeting Connectors though.
Are we sure this got propagated to the EU Cluster ?

All API calls still returns “null” (for this Request).

Rgs,
Bo

23

Hey @bo.staahle,

Unfortunately we had to delay this release a few days. Stay updated here:

Thanks. for your patience,
Tommy

24

Hey @bo.staahle,

This has now been released! :slight_smile: We have also updated the docs!

Thanks,
Tommy

25

Hi Tommy,

Bad news, still not working for Meeting Connector.

New syntax working for Room Connectors.

Just tested now from around 11:00-11:25 CEST

All ends up with
image

Unless no list given and the system selects all registered Zone Controllers.

payload = “{“share_mc”:true}” # Sets True and selects all
#payload = “{“share_mc”:true,“meeting_connector_list”:[“185.174.117.51:8802”]}” # Sets True and selects None
#payload = “{“share_mc”:true,“meeting_connector_list”:[“185.174.117.51”]}” # Sets True and selects None
#payload = “{“meeting_connector_list”:[“185.174.117.51:8802”]}” # No effect
#payload = “{“meeting_connector_list”:[“185.174.117.51”]}” # No effect
#payload = “{“share_mc”:true,“meeting_connector_list”:[“pkg|tcp://185.174.117.51:8802”]}” # Sets True and selects None
#payload = “{“share_mc”:true,“meeting_connector_list”:[”;pkg|tcp://185.174.117.51:8802, “]}” # Sets True and selects None

This time I did most of the tests both from API Reference, via api.zoom.us and eu01web.zoom.us

The Patch still returns null btw, don’t know if that helps figuring something out.

image

PATCH https://api.zoom.us/v2/accounts/nwwVhdJxTLS6LY2QnmcFww/options

Headers:
Authorization: Bearer XXXX
Content-Type: application/json

Body:
{
“meeting_connector_list”: [
“185.174.117.51”,
“185.174.117.52”
],
“share_mc”: true
}

Regards,
Bo

26

Thanks for reporting this @bo.staahle!

We are looking into it and will provide you an update.

-Tommy

27

Hey @bo.staahle,

For meeting connector, please try the following payload format:

{
"meeting_connector_list": [
";pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443,"
],
"share_mc": true
}

By searching, ";pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443," should be a valid single complete meeting connector.

Thanks,
Tommy

28

Hi Tommy,

That actually works.

As well as setting at least two (what I have tested so far :wink: )

Thank you very much.

Regards,
Bo

1 Like
29

You are welcome! :slight_smile:

Thanks for your patience during these updates!

-Tommy