# API for a cloud recording status

**URL:** <https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228>\
**Category:** API and Webhooks\
**Created:** [April 30, 2018, 5:52pm UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228 "2018-04-30T17:52:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mihir\_Matalia](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@Mihir\_Matalia](https://devforum.zoom.us/u/Mihir_Matalia)\
**Post date:** [April 30, 2018, 5:52pm UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228/1 "2018-04-30T17:52:11Z")

</div>

I am using API to retrieve all the recordings of a meeting:

[https://api.zoom.us/v2/meetings/{{meetingId}}/recordings](https://api.zoom.us/v2/meetings/%7B%7BmeetingId%7D%7D/recordings)

In between the time when meeting is over and the cloud recording is processed, is there a way to get relevant response ? as of now, during that time I get response of there&nbsp;is no recording for this meeting

{  
&nbsp; &nbsp; &nbsp;“code”: 3301,  
&nbsp; &nbsp; &nbsp;“message”: “There is no recording for this meeting”  
}

with this response, it’s hard to write proper response management code

---

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [April 30, 2018, 8:04pm UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228/2 "2018-04-30T20:04:35Z")

</div>

We’ve dealt with the same issue.

The best strategy until the API changes so that a more helpful response is given is just to store the data from the webhook notification somewhere and then&nbsp;wait at least 10 minutes before retrieving the file.

---

<div class="post-metadata">

**Author:** ![Zoom\_Developer](https://avatars.discourse-cdn.com/v4/letter/z/eb8c5e/32.png) [@Zoom\_Developer](https://devforum.zoom.us/u/Zoom_Developer)\
**Post date:** [May 10, 2018, 3:49am UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228/3 "2018-05-10T03:49:39Z")

</div>

Have you considered using our notification framework ? you can essentially enable an event notification for recording completion and get your webhook triggered … that’s our recommended option.&nbsp;

---

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [May 10, 2018, 4:57am UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228/4 "2018-05-10T04:57:22Z")

</div>

So, maybe the original poster is not using the webhook notifications but I am and I have found through practice the recordings are often not ready to download when the recording completed notification is sent. I was able to avoid these errors by setting up my project so that it stores the information received from the recording completed notification and waits at least 5-10 minutes before making the call to download the recordings.

---

<div class="post-metadata">

**Author:** ![Zoom\_Developer](https://avatars.discourse-cdn.com/v4/letter/z/eb8c5e/32.png) [@Zoom\_Developer](https://devforum.zoom.us/u/Zoom_Developer)\
**Post date:** [May 10, 2018, 5:16am UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228/5 "2018-05-10T05:16:35Z")

</div>

we will investigate this - when your app gets the notification from us with the download URL, the files&nbsp;should be available for download immediately.&nbsp; &nbsp;We will ask our team to do some testing and see if we can reproduce this. Let’s nail this down so that you don’t have to add workarounds on your side.&nbsp;

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 5:41pm UTC](https://devforum.zoom.us/t/api-for-a-cloud-recording-status/1228/6 "2020-08-21T17:41:15Z")

</div>

Closed on August 21, 2020, 5:41pm UTC


