Websockets limitations

[j.c.novoa_zoom (J.C.)]

We are currently connecting to seperate 3 marketplace apps within our zoom account.

1 for ZCC
1 for ZMeetings
1 for Zoom Phone.

Each market place app is setup for Websocket events. When we connect to the websocket URL for the first market place app, we get a successful connection, when we. connect the the 2nd websocket url (while the 1st is still active)…we get an error in the connection “Connected in another place”

Is there a limit to how many websocket connections you can have in an account? If so what limits? To recieve websocket events for all 3 services, is the recommendation to use a single marketplace app that supports ALL 3 services?

[gianni.zoom (Gianni)]

Hi @ojus.zoom can you please help this developer with their use case?

[intropy]

I’ve received an event:

{
    "module": "close_connection",
    "success": "True",
    "content": "Connected in another place",
    "header":
    {} ...
}

Same questions here:
How often can you subscribe to a WebSocket?
Does it matter if you have another (new) OAuth token?
How can I scale my service to listen to WebSocket events if I can only establish one connection?

Any insight or recommendations are appreciated.

[ojus.zoom (Ojus)]

@j.c.novoa_zoom @intropy thanks for bringing this to our attention.

typically for a given WebSocket subscription you can only open one subscription at a time.

If you are saying that you have independent websocket subscriptions and they aren’t running concurrently, then this is a bug. Can you please confirm?

[intropy]

Right now, I have one wss:// endpoint in one Zoom App.
The service subscribes to it fine.
As soon as a second instance tries to subscribe to the same endpoint (but with a different token) the first connection gets closed. I guess it depends on what is meant by “independent subscription”.

I was falsely under the impression both subscriptions would be able to receive events or that there would be some sort of round-robin on who will get an event on multiple subscriptions.

My only option to achieve some redundancy and fault tolerance is to create a second identical wss:// endpoint. Am I right with this assumption @ojus.zoom?

[ojus.zoom (Ojus)]

@intropy thats correct