Zoom User endpoint is not recognizing the dates in the parameter field correctly.
For example, if I do users/[userID]/recordings?from=2025-06-05&to=2025-06-21 then the dates that pop out are 2025-06-16 to 2025-06-17.
Hi @Dongkeun
Thanks for reaching out to us and welcome to the Zoom Developer Forum.
Can you please share the entire request URL you are sending, the response body and also the tracking ID found in the request headers so I can look further into this please?
for example,
URL: Endpoint: /v2/users/7CU0eW-CTxCM3IO1-nGFew/recordings
Params: from=2025-05-15, to=2025-06-01
Response body: {
“from”: “2025-06-19”,
“to”: “2025-06-20”,
“page_count”: 1,
“total_records”: 1,
“meetings”: [
{
“uuid”: “qanWAaKESDesjcc+c717wQ==”,
“id”: 89468745582,
“topic”: “MH Rounds”,
“start_time”: “2025-06-19T20:10:20Z”,
…
}
]
}
Tracking ID:
v=2.0;clid=us06;rid=WEB_7d0d61ebcad9cd93178e5709a47ad28b
It used to work - I played around with this endpoint maybe 100 times and it always sent back the correct dates
1 Like
hi @Dongkeun ,
Could you please try to keep date ranges within the same month.
Recordings are held in a way that big date range quiries can fail.
Please check wihtin the same month.
all the best
John Drinkwater
Hi @Dongkeun , I had faced this similar situation with the messages API. Not sure if itll help, But you can try. Please try with strings like 2025-06-19T00:00:00Z not just YYYY-MM-DD , This gave me the expected response. Cheers. Let me know if this fixes .
Update: Tested out, The above suggested approach didnt work for me. @Dongkeun , I am facing this same problem now even for endpoint: /report/users/{user_id}/meetings . I have been playing around with both these APIs for quite some time and it gave proper results, Not working as expected Now. This issue seems to have appeared just since these few days.
Yes, it doesn’t work. I also tried to keep it in the same month and that didn’t work either. What’s the best way forward now?
cc @expertswho
can you please surface this issue up to the team and get them to fix it? it feels like a bug on Zoom’s side and it’s impacting my worflow
Hey @Dongkeun
Looking into this right now.
Can you confirm if you were expecting more recordings in this call?
URL: Endpoint: /v2/users/7CU0eW-CTxCM3IO1-nGFew/recordings
Params: from=2025-05-15, to=2025-06-01
Response body: {
“from”: “2025-06-19”,
“to”: “2025-06-20”,
“page_count”: 1,
“total_records”: 1,
“meetings”: [
{
“uuid”: “qanWAaKESDesjcc+c717wQ==”,
“id”: 89468745582,
“topic”: “MH Rounds”,
“start_time”: “2025-06-19T20:10:20Z”,
…
}
]
}
Tracking ID:
v=2.0;clid=us06;rid=WEB_7d0d61ebcad9cd93178e5709a47ad28b
thank you, and i was. and the dates that were returned above are completely incorrect.
1 Like
Thanks @Dongkeun , I will create a ticket with our Engineering team. I am not able to replicate this on my end.
As @expertswho suggested, when i use date ranges within the same month I do not have an issue
thank you. it definitely doesn’t work for me.
here’s another example with the same month dates and doesn’t work
URL: Endpoint: /v2/users/7CU0eW-CTxCM3IO1-nGFew/recordings
Params: from=2025-05-15, to=2025-05-31
{
“from”: “2025-06-24”,
“to”: “2025-06-24”,
“page_count”: 1,
“page_size”: 30,
“total_records”: 1,
“next_page_token”: “”,
“meetings”: [
{
“uuid”: “t8G+SZpHQsOGGhgBdzHUNg==”,
“id”: 89468745582,
“topic”: “MH Rounds”,
…
}
]
}
Tracking ID;
v=2.0;clid=us06;rid=WEB_c71ed7fb884c7f3f0edf8575f8126bd4
1 Like
Thanks again @Dongkeun
I created an internal ticket for our Engineering team (ZSEE-171463 internal ticket number just for reference)
Hi @Dongkeun
Thanks for your patience here. Our Engineering team reached out back to me and shared that they were able to look into the logs and it seems like you are passing additional dates in your query params.
Can you please verify your request and make sure you are only passing one date on each param?
Appreciate you getting back.
I dont understand what they mean by additional dates. Even if I put in one date, it’s wrong. Here’s an example. (I used a different user id just in case and still wrong)
URL: Endpoint: /v2/users/EKQvNbF2TrCChxDm7p4P4w/recordings
Params: from=2025-05-15
Response Body:
“from”: “2025-06-26”,
“to”: “2025-06-26”,
“page_count”: 1,
“page_size”: 30,
“total_records”: 3,
“next_page_token”: “”,
“meetings”: [
{
“uuid”: “zo4/wRksRemWbRgzCd11zg==”,
“id”: 87417567608,
…
}
]
}
TrackingID:
v=2.0;clid=us06;rid=WEB_8eea9dd3e14de5b3ee193be34892b52f
I’ve also done this 100s of times successfully so I’m pretty sure I didn’t put an extra date parameter. Is there a way I can get a video call with them so we can debug this issue?
Could there be something wrong with how the API reads the query params? I’m definitely only putting in one. And Zain above also encountered the same issue
hi @Dongkeun
I can hop on a call with you to see what the issue could be.
I will send you a link to a meeting via DM
Thanks for meeting with me @elisa.zoom!
Matter resolved: looks like it was an error on the API client, not Zoom’s side
2 Likes
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.