Active Session Not Returned by /videosdk/sessions API

Video SDK Web
,
1

Description
I made an API request to /videosdk/sessions with the parameter session_name=2303457008_1747637230356 at "2025-05-22T15:33:12+09:00", but the response I received was empty.

However, at that exact time, I had an active session with the ID BtO+9ZrWS+uneAТ+mipkqw==, which was running from "2025-05-22T15:33:07+09:00" to "2025-05-22T16:17:35+09:00".

Could you please check the logs for me? I would like to understand why the API returned incorrect data.

Which Web Video SDK version?
2.1.0

2

@vic.yang I would appreciate it if you could look into this issue.
I look forward to hearing from you soon.
Thank,
Phuong

1 Like
3

Hey @phuongnv1

Thanks for your feedback.

BtO+9ZrWS+uneAТ+mipkqw==

We searched the session ID in our system but couldn’t find any session that matches it.

Thanks
Vic

4

@vic.yang It seems the sessionId might contain incorrect Unicode characters.
Could you please help check the session ID BtO+9ZrWS+uneAT+mipkqw==?
Thanks
Phuong

5

@vic.yang I’d really appreciate it if you could take a look soon.
Your help would be very much appreciated.
Thanks
Phuong

6

Hi @phuongnv1

Could you share the x-zm-trackingid value from the response headers with us for troubleshooting?

Thanks
Vic

7

@vic.yang Currently, we are unable to retrieve the x-zm-trackingid header on our side.
However, I believe the logs should contain basic information such as the request timestamp and the parameters (payload) sent.
Would it be possible for you to check the logs using these details?

Thanks
Phuong

8

@vic.yang
Is this a limitation of the Zoom Video SDK?
Can I configure my Zoom account so that the API can access data in real time? (For example, as a paid feature option)

I would appreciate your feedback.

Thanks
Phuong

9

@vic.yang
I continue to encounter a similar issue. Could you please help me check with x-zm-trackingid equal to "v=2.0;clid=aw1;rid=WEB_fa8ae0be2c3ff7164814f30ed440c818"?

I look forward to hearing back from you.

Thanks
Phuong

10

@vic.yang
I’ve sent the x-zm-trackingid. Could you please check the logs for me so I can better understand how to handle this issue?

I would appreciate your feedback.

Thanks
Phuong

11

Hey @phuongnv1

v=2.0;clid=aw1;rid=WEB_fa8ae0be2c3ff7164814f30ed440c818

We found that in this query, the session_name parameter did not match any active sessions, so the result returned was empty.

If you encounter this issue again, could you please share the session_name, from, and to parameters, along with the x-zm-trackingid value for further troubleshooting?

Thanks
Vic

12

Hey @vic.yang ,
Thank you for your response.

I would like to further clarify this case. For the request with x-zm-trackingid set to v=2.0;clid=aw1;rid=WEB_fa8ae0be2c3ff7164814f30ed440c818, we sent the following parameters:

{ type: 'live', session_name: '8438180395_1748686843824' }

The request was made at 2025-05-31T10:22:00.745Z, during which a session with sessionId OuZXjWsYQ7+i5B7lCaAhvA== was active. This session started at 2025-05-31T10:21:56Z and ended at 2025-05-31T10:24:11Z. Based on the session time and the request time, returning an empty data response appears to be incorrect.

I hope you can help clarify this issue.

Thanks
Phuong

13

Hey @vic.yang
Could you please help me check the detailed logs?
I would appreciate your feedback.
Thanks
Phuong

14

Hi @phuongnv1

Thanks for providing the detailed information.

We analyzed the logs and tried to reproduce the issue, but were unsuccessful. We may need your further assistance to identify the root cause.

  • Is it that all sessions cannot be found using session_name, or only some sessions? If it’s only some, do those sessions have any particular characteristics?

  • Can the sessions be found if you remove the session_name condition?

  • Can you find past sessions using session_name?

Thanks
Vic

15

Hey @vic.yang

We analyzed the logs and tried to reproduce the issue, but were unsuccessful.

It seems that if the query is executed within 3 to 4 seconds after the session starts, no results are returned. In other cases, it works fine. Could you try to reproduce the issue based on that scenario?

  • Is it that all sessions cannot be found using session_name, or only some sessions? If it’s only some, do those sessions have any particular characteristics?

Currently, a few sessions are experiencing this issue, even though there’s no apparent difference compared to other sessions.

  • Can the sessions be found if you remove the session_name condition?

Since our case requires finding active sessions based on the session_name, I haven’t been able to test that scenario yet. However, I suspect it’s experiencing the same issue, as mentioned earlier — if the query is made within the first 3 to 4 seconds, no results are returned.

  • Can you find past sessions using session_name?

Retrieving past sessions based on the session_name is still working as expected.

Thanks
Phuong

16

Hey @phuongnv1

It seems that if the query is executed within 3 to 4 seconds after the session starts, no results are returned. In other cases, it works fine.

Yes. It’s by design. We recommend querying the active sessions after the session has been running for at least 10 seconds. The RESTful API is not real-time and may take some time to reflect the updated session status.

Thanks
Vic

1 Like
17

Hey @vic.yang
Thank you for your response.
I would also like to confirm whether, when using the /videosdk/sessions/{sessionId}/users API to retrieve the list of users in a live session, the returned data might differ from the actual number of users currently in the session.

Thanks
Phuong

18

Hi @phuongnv1

the returned data might differ from the actual number of users currently in the session

Which part is different? Could you provide a detailed example? Would the issue be resolved if you wait a bit before querying again?

Thanks
Vic

19

@vic.yang
Let me explain the flow of my case in more detail:

  • Frontend: It checks if there is any user other than user A (e.g., a new user B joins). If so, it calls the /example API.
  • Backend: Within the /example API, it then calls /videosdk/sessions/{sessionId}/users to retrieve the list of users in the session. However, the response only includes user A.

Could this be the same issue we previously discussed regarding retrieving data from a live session?

Thanks
Phuong

20

Hi @phuongnv1

Could this be the same issue we previously discussed regarding retrieving data from a live session?

Yes.

You can try using webhooks to listen for the user joined event. This allows the Backend to more accurately determine the right timing to call the API.

session.user_joined
Video SDK Webhooks

Thanks
Vic

​