# Expose createdAt UNIX timestamp on RoomData

**URL:** <https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283>\
**Category:** Suggestions\
**Created:** [April 7, 2023, 11:25pm UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283 "2023-04-07T23:25:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/kevin/32/410_2.png) [@Kevin](https://community.coherence.io/u/Kevin)\
**Post date:** [April 7, 2023, 11:25pm UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283/1 "2023-04-07T23:25:46Z")

</div>

When building a UI that lists the available rooms it would be helpful to have data about when the room was created. For my specific use case, I would use this data (ideally a UNIX timestamp) to sort the list of rooms.

From what I can tell, this information is not currently available. As a work around, I could envision storing the timestamp as as KV pair when creating the room, but this is of course subject to clients being malicious, so less ideal.

![image](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/beebb5970dfb4f5b45ffd945ef2a1db7fe200345.png)

Please let me know if I am missing something obvious. Thanks 🙂 .

---

<div class="post-metadata">

**Author:** ![per\_coh](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/per_coh/32/27_2.png) [@per\_coh](https://community.coherence.io/u/per_coh)\
**Post date:** [April 13, 2023, 7:36am UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283/2 "2023-04-13T07:36:06Z")

</div>

And thanks for that one @Kevin . Added this one too.

---

<div class="post-metadata">

**Author:** ![per\_coh](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/per_coh/32/27_2.png) [@per\_coh](https://community.coherence.io/u/per_coh)\
**Post date:** [October 2, 2023, 12:03pm UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283/3 "2023-10-02T12:03:52Z")

</div>

Late reply, but this should be sorted now.

---

<div class="post-metadata">

**Author:** ![Kevin](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/kevin/32/410_2.png) [@Kevin](https://community.coherence.io/u/Kevin)\
**Post date:** [October 2, 2023, 3:06pm UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283/4 "2023-10-02T15:06:51Z")

</div>

Awesome to hear, thanks!

Is this new field covered in any existing docs?

---

<div class="post-metadata">

**Author:** ![ciro](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/ciro/32/82_2.png) [@ciro](https://community.coherence.io/u/ciro)\
**Post date:** [October 4, 2023, 9:39am UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283/5 "2023-10-04T09:39:53Z")

</div>

> [@Kevin](#):
>
> Is this new field covered in any existing docs?

Hey Kevin, yes, as of a couple of months ago we have **[API Reference docs](https://unityapi.coherence.io/docs/v1.0.0/index.html)**, so you can find this parameter (and more) on the [**RoomData struct page**](https://unityapi.coherence.io/docs/v1.0.0/api/Coherence.Cloud.RoomData.html?q=roomdata#Coherence_Cloud_RoomData_CreatedAt).

We still need to add details to all parameters, hopefully most of them are self explanatory! 🤞  
For the rest, just ask! 🙂

---

<div class="post-metadata">

**Author:** ![Ahti](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/ahti/32/216_2.png) [@Ahti](https://community.coherence.io/u/Ahti)\
**Post date:** [October 5, 2023, 8:15am UTC](https://community.coherence.io/t/expose-createdat-unix-timestamp-on-roomdata/283/6 "2023-10-05T08:15:40Z")

</div>

Hey Kevin, as a bonus we’ve also updated the **[Rooms](https://docs.coherence.io/coherence-cloud/configure-rooms)** article in our docs (it now has a screenshot of the UI as well as a more clear list of what’s shown). Hope it helps! 🙂