# Cloud Recordings Identification

**URL:** <https://devforum.zoom.us/t/cloud-recordings-identification/133551>\
**Category:** Web\
**Tags:** recording\
**Created:** [June 3, 2025, 8:21am UTC](https://devforum.zoom.us/t/cloud-recordings-identification/133551 "2025-06-03T08:21:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ben17](https://avatars.discourse-cdn.com/v4/letter/b/ba8739/32.png) [@Ben17](https://devforum.zoom.us/u/Ben17)\
**Post date:** [June 3, 2025, 8:21am UTC](https://devforum.zoom.us/t/cloud-recordings-identification/133551/1 "2025-06-03T08:21:49Z")

</div>

We would ideally like to be able to identify where multiple recordings happened in a single “meeting”. The only way we have found currently is to start recording, then make our own timestamp record, then after the recordings are processed we can match recordings using our saved timestamps.  
So my question is. Is there any other method available to identify where recordings came from, eg. pass custom meta data or an id to the recording when recording is started?

---

<div class="post-metadata">

**Author:** ![ticorrian.heard](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ticorrian.heard/32/70213_2.png) [@ticorrian.heard](https://devforum.zoom.us/u/ticorrian.heard)\
**Post date:** [June 5, 2025, 6:20pm UTC](https://devforum.zoom.us/t/cloud-recordings-identification/133551/2 "2025-06-05T18:20:59Z")

</div>

Hi @Ben17 Would you be able to use the [recording.started](https://developers.zoom.us/docs/api/meetings/events/#tag/recording/POSTrecording.started) webhook and create an ID based off the timestamp in the request payload?

---

<div class="post-metadata">

**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:** [June 5, 2026, 6:21pm UTC](https://devforum.zoom.us/t/cloud-recordings-identification/133551/3 "2026-06-05T18:21:40Z")

</div>

Closed on June 5, 2026, 6:21pm UTC

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
