# DeepLink expiry

**URL:** <https://devforum.zoom.us/t/deeplink-expiry/81277>\
**Category:** Zoom Apps\
**Created:** [January 11, 2023, 2:54pm UTC](https://devforum.zoom.us/t/deeplink-expiry/81277 "2023-01-11T14:54:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesoughton](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jamesoughton/32/18552_2.png) [@jamesoughton](https://devforum.zoom.us/u/jamesoughton)\
**Post date:** [January 11, 2023, 2:54pm UTC](https://devforum.zoom.us/t/deeplink-expiry/81277/1 "2023-01-11T14:54:18Z")

</div>

We are creating a DeepLink on an app outside Zoom. How long does this deeplink stay valid for, is there an expiry period that we can plan around? I assume that an expired deeplink uri will result in an error on the zoom client - can you please tell me what this error could be so we could test for it?

thanks

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [January 18, 2023, 1:50am UTC](https://devforum.zoom.us/t/deeplink-expiry/81277/2 "2023-01-18T01:50:59Z")

</div>

I’m checking with our engineering team on this and will get back to you when I have more information.

---

<div class="post-metadata">

**Author:** ![avinash](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/avinash/32/44229_2.png) [@avinash](https://devforum.zoom.us/u/avinash)\
**Post date:** [August 11, 2024, 3:05am UTC](https://devforum.zoom.us/t/deeplink-expiry/81277/3 "2024-08-11T03:05:03Z")

</div>

@MaxM Any update on this?

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [August 14, 2024, 5:50pm UTC](https://devforum.zoom.us/t/deeplink-expiry/81277/5 "2024-08-14T17:50:19Z")

</div>

I wasn’t able to find the ticket that I created for this so I reached out to our team directly. I’ll update this thread as soon as I hear back from them.
