# Zoom Event Ordering & Unique Identifiers **URL:** \ **Category:** API and Webhooks\ **Created:** [November 13, 2023, 12:43pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279 "2023-11-13T12:43:23Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![amp3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp3/32/49141_2.png) [@amp3](https://devforum.zoom.us/u/amp3)\ **Post date:** [November 13, 2023, 12:43pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279/1 "2023-11-13T12:43:23Z")
**API Endpoint(s) and/or Zoom API Event(s)** _Link the API endpoint(s) and/orZoom API Event(s) you’re working with to help give context._ Zoom Operation Logs Endpoint **Description** _Details on your question, workflow or the problem you’re trying to solve._ I’m working in ingesting Zoom logs and I’m trying to ensure we’re not duplicating logs. It appears that there’s no unique identifier for each log other than the timestamp. I’m wondering if the millisecond timestamp offers enough granularity to be a unique identifier? If a user performs a two actions at the same time, is it possible there will be two identical logs? If timestamps are not unique, I’m considering creating an index of the position of the log within each page and I’m wondering when the data settles for Zoom’s REST API? From testing, it appears that new logs are added to the beginning to the response. Will there ever be a situation where logs will be added to another position in the list, or are new events always prepended? Thanks! ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [November 14, 2023, 1:37pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279/2 "2023-11-14T13:37:06Z")
Hi @amp3 Thanks for reaching out to us. This is a great question. Please allow me to do some testing on my end and I will get back to your with an update. ---
**Author:** ![amp3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp3/32/49141_2.png) [@amp3](https://devforum.zoom.us/u/amp3)\ **Post date:** [November 16, 2023, 5:54pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279/3 "2023-11-16T17:54:38Z")
@elisa.zoom Any update? Thanks! 🙂 ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [November 16, 2023, 7:55pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279/4 "2023-11-16T19:55:40Z")
Hi @amp3 Thanks for your patience here, from my testing, it looks like the timestamp is pretty accurate and they do come in order of execution. I do see how an index number or an ID could be helpful. Please add that suggestion in our feature request section > **[Feature Requests](https://devforum.zoom.us/c/feature-requests/23)** > > Have an API or SDK feature request? Share it here! ---
**Author:** ![amp3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp3/32/49141_2.png) [@amp3](https://devforum.zoom.us/u/amp3)\ **Post date:** [November 17, 2023, 3:44pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279/5 "2023-11-17T15:44:02Z")
Thanks @Elisa! I appreciate your help and will add a feature request for a unique identifier! ---
**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 18, 2023, 3:44pm UTC](https://devforum.zoom.us/t/zoom-event-ordering-unique-identifiers/98279/6 "2023-11-18T15:44:40Z")
Closed on November 18, 2023, 3:44pm UTC This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.