API bug — List of trashed recordings returns empty if all recordings are in the trash

Description

:warning: This issue should be a high priority since after 30 days recordings are deleted permanently!

I’m glad I caught this issue before I experienced data loss…

When trying to get the list of recordings in the trash, the list is empty if ALL recordings are in the trash!

However, if I recover at least one of the recordings, then all the remaining trashed recordings are returned in the list.

Currently I only have a manual work-around (without doing something like creating a nonce meeting/recording via the API) since the script has no way to detect the presence of recordings in the trash.

Error
There is no error message, which makes this problem even worse, because it fails silently!

The problem is unexpected/incorrect behavior.

When I make the call I get an HTTP Status Code: 200 which is what I expect, but the meetings list is empty if all of the recordings are in the trash.

Which App Type (OAuth / Chatbot / JWT / Webhook)?
OAuth

Which Endpoint/s?
https://api.zoom.us/v2/users/me/recordings

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. First make sure that all recordings are in the trash
  2. Make a call to https://api.zoom.us/v2/users/me/recordings?trash=true&page_size=300 which results in:
<Response [200]>
{'page_count': 0, 'page_size': 0, 'total_records': 0, 'next_page_token': '', 'meetings': []}
  1. Then recover a single recording, but leave all of the rest in the trash.
  2. Make the same call to https://api.zoom.us/v2/users/me/recordings?trash=true&page_size=300 which results in:
<Response [200]>
{'page_count': 1, 'page_size': 300, 'total_records': 1, 'next_page_token': '', 'meetings': [{'uuid': 'pjE2FEGrRrWo5Sdxtz4WqQ=='
...snip...

Additional context
This issue seems to be fairly new, because my scripts were working fine a few weeks ago, however recently this behavior/bug in the API seems to have appeared. Luckily I noticed it before some of my recordings were permanently expunged!

Hi @aculich,

Thank you for raising this with us, and our apologies for the trouble! I have been able to reproduce this and have brought it to the attention of our Engineering team. (ZOOM-287245)

Thanks again,
Will

1 Like

Hey @aculich,

Just a quick note to confirm that this bug is currently being worked on and we hope to have a fix released in a few weeks. (ZOOM-287245)

Thanks again for your diligence in reporting it.

Thanks!
Will

1 Like

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