The zoom call recording API v2 does not support “from” and “to” date parameters. I am trying to create a call recordings list where the admins can view users’ call recordings from a specific date range. The API documentation also says it will return “from” and “to” but it does not.
Hey @john1, thanks for posting and using Zoom!
Unfortunately the GET Users Phone Recordings uses pagination and not a date filter.
We will fix this in our docs. CC @shrijana.g
Sorry for the confusion, @john1. Thank you for letting us know. We have fixed the documentation.
Hello Tommy and Shrijana; Do you plan to include search by date? That is an important feature for us. We are coming over from RingCentral and they have a million bells and whistles. The search function is really important.
Further, do you plan to include phone number search? That is also very important and I don’t see these features being difficult to implement.
Please advise. Thanks!
Can you elaborate on “Phone Number Search”? Are you searching for numbers in your account or?
I will add these suggestions as feature requests!
Hi Tommy: We have a small call center and our agents make between 300 and 500 calls per day, and they are recorded. We like to audit the calls, especially the ones where they set a meeting. We want to go back and listen to the call. We would have a difficult time searching through hundreds of numbers. There is no search function so we would have to go page by page… kind of ridiculous. I’m sure you’ll agree.
Also, it would help if we could search by date for obvious reasons.
Does that make sense?
For further questions or clarifications, please call Jared Moore at 774-766-8804.
My Best Always,
You can GET Phone Recordings by user using this endpoint.
I will pass this feedback to our team for consideration.
Hey Zoom Team - are there any updates on allowing us to use
to parameters for filtering recordings in the phone APIs?
We’d like to see
to implemented on user call recordings, voicemails and the new call queue recordings API.
No updates yet, but it is in our backlog to implement. (ZOOM-180612)