# Fetching recordings using session\_name **URL:** \ **Category:** Web\ **Created:** [October 31, 2024, 5:55pm UTC](https://devforum.zoom.us/t/fetching-recordings-using-session-name/120138 "2024-10-31T17:55:50Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![alanc](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/alanc/32/49397_2.png) [@alanc](https://devforum.zoom.us/u/alanc)\ **Post date:** [October 31, 2024, 5:55pm UTC](https://devforum.zoom.us/t/fetching-recordings-using-session-name/120138/1 "2024-10-31T17:55:50Z")
**API Get Recordings** Dev zoom url → path: docs/api/rest/reference/video-sdk/methods/#operation/recordingGet **Description** I’m thinking if it’s possible to fetch recordings based on session\_name. The reasoning for this is the following: On a normal call I only create one session\_id. On a different call but both users left the room and then rejoined later, I saw that zoom creates a new session\_id but with same session\_name as I defined previously but adding a session\_key with my previous session\_id. The part that zoom creates a new session\_id and I only get notified at the frontend leaves me with my DB unsynced. Right now I’m having a hard time for this scenario to keep my DB in sync, if I could query recordings based on session\_name that should solve all of my issues. Or if you have a way to solve this I’m all ears. ---
**Author:** ![ekaansh.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ekaansh.zoom/32/55004_2.png) [@ekaansh.zoom](https://devforum.zoom.us/u/ekaansh.zoom)\ **Post date:** [November 5, 2024, 11:59am UTC](https://devforum.zoom.us/t/fetching-recordings-using-session-name/120138/2 "2024-11-05T11:59:23Z")
@alanc There are two ways to solve this: 1. You can use `client.getSessionInfo().sessionId` to get the `sessionId` and sync that with your database. You can see an example of this in our [Telehealth sample app](https://github.com/zoom/VideoSDK-Web-Telehealth/blob/17537e2009612e24e8e0c5abacc64ed153a7ab29/src/components/videocall/Videocall.tsx#L36). We store all different sessionIds for a single “session name” in the database. We can then [query those recordings](https://github.com/zoom/VideoSDK-Web-Telehealth/blob/17537e2009612e24e8e0c5abacc64ed153a7ab29/src/server/api/routers/zoom.ts#L32) using the API. 2. This is **not** something I would recommend since we rate limit the API but you can also query all sessions and recursively get the recordings as a last resort. [Link to code](https://github.com/zoom/VideoSDK-Web-Telehealth/blob/f064caafe78c35ea82d6ef7adc18addd35a1b8a5/src/server/api/routers/zoom.ts#L7) ---
**Author:** ![alanc](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/alanc/32/49397_2.png) [@alanc](https://devforum.zoom.us/u/alanc)\ **Post date:** [November 5, 2024, 6:33pm UTC](https://devforum.zoom.us/t/fetching-recordings-using-session-name/120138/3 "2024-11-05T18:33:37Z")
Actually, it would be a significant lift for us to implement option #1, as all we’re trying to do is avoid closing the session on a simple browser refresh. We’re hoping to increase the call threshold for a couple of minutes after the session ends, rather than immediately destroying it, similar to the “EmptyRoomTimeout” parameter from Twilio twilio-dot-com/docs/video/api/rooms-resource#request-body-parameters-1 Implementing this threshold would be extremely helpful for cases where the user refreshes the page or briefly disconnects without requiring a full session reinitialization. Thanks again for your help! @ekaansh.zoom ---
**Author:** ![ekaansh.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ekaansh.zoom/32/55004_2.png) [@ekaansh.zoom](https://devforum.zoom.us/u/ekaansh.zoom)\ **Post date:** [November 6, 2024, 11:31am UTC](https://devforum.zoom.us/t/fetching-recordings-using-session-name/120138/4 "2024-11-06T11:31:57Z")
Hey @alanc I understand your use-case, but this isn’t supported at the moment. The recommended way to keep sessions alive is by adding a linux client to the meeting, which again wouldn’t be ideal for what you’re trying to do. It would require some engineering effort still. I’ll check with the product team if we can add a timeout wait feature to the roadmap, but it’s not a supported use-case at the moment. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [November 10, 2025, 3:08am UTC](https://devforum.zoom.us/t/fetching-recordings-using-session-name/120138/5 "2025-11-10T03:08:12Z")
Closed on November 10, 2025, 3:08am UTC This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.