Zoom meetings API now ignores 'from' and 'to' parameters

API and Webhooks Meetings
1

API Endpoint /users/{userId}/recordings now ignores from and to parameters.

URL /v2/users/6kGvjzUnQeSDKJKMu-NTTw/recordings?from=2025-01-15T00:00:00Z&to=2025-01-16T00:00:00Z&page_size=100&next_page_token=

from=2025-01-15T00:00:00Z&to=2025-01-16T00:00:00Z

Response body:
{
“from”: “2025-06-29”,
** “to”: “2025-06-30”,**
“page_count”: 1,
“page_size”: 100,
“total_records”: 1,
“next_page_token”: “”,
“meetings”: [
{
“uuid”: “BIWMaQqyTgG/1HbdpEl4mQ==”,
“id”: 86283043406,
“account_id”: “POEdjIgdRluvSC5bKja0_g”,
“host_id”: “421Hw4QiTnuC7VK4ak8J7w”,
“type”: 1,
“start_time”: “2025-06-30T13:09:38Z”,
…

I had this application working fine for several years. Lately it started malfunctioning. It now ignores date parameters and returns the latest meetings.

Zoom customer support gave me runaround on the ticket stating they have no resources to fix their own bugs and directed me to this forum.

@elisa.zoom

2

Hi @Aleksandr2
Thanks for reaching out to us.
I recently helped a developer with a similar issue and it was an issue with the client they were using to call our API.
Do you have a script running or how are you making this API call?
Would it be possible for you to test this using a tool like Postman?

3

Hi @Elisa via Zoom Developer Forum

I call it from a C# application that’s been running for several years with no problems.

Yes, I can test it with Postman.

5

I don’t know what you mean by sub-day filtering. ‘To’ and ‘from’ parameters are a supported feature. I had my application working fine like this for several years. It’s just recently it started to malfunction ignoring these parameters

6

Thanks @Aleksandr2
Could you please share with me a request URL you recently sent as well as the tracking ID in the response headers so I can escalate this please

And just confirming, where you able to reproduce this behavior using Postman?

8

Hello! I’m having a similar issue with the contact center api, its compeletely ignoring by date parameters.

p = {

  "timezone": "America/Chicago",

  "from": "2025-08-01T00:00:00Z",

  "to": "2025-08-03T00:00:00Z"

}

res = requests.get("https://api.zoom.us/v2/contact_center/analytics/log/historical/engagement", headers=h,params=p).json()

engagements = res['engagements']

Response :

{‘next_page_token’: ‘KIuJBJ7EfOX1rbCf2qzQ6ME62t4sfN6mLd2’, ‘page_size’: 10, ‘total_records’: 118081, ‘from’: ‘2025-08-01T00:00:00Z’, ‘to’: ‘2025-08-03T00:00:00Z’, ‘timezone’: ‘America/Chicago’, ‘engagements’: [{‘engagement_id’: ‘29BdmH1MTiWfNFz7nhoV1Q’, ‘direction’: ‘inbound’, ‘channels’: [{‘channel’: ‘voice’, ‘channel_source’: ‘voice’}], ‘enter_channel’: {‘channel’: ‘voice’, ‘channel_source’: ‘voice’}, ‘start_time’: ‘2025-08-14T14:06:09Z’, ‘end_time’: ‘2025-08-14T14:08:03Z’, ‘consumer’: {‘consumer_number’: ‘+15123715800’}, ‘queues’: [{‘queue_id’: ‘VH5zdFheTKGJHYioZ8ueXg’, ‘queue_name’: ‘Agent Support Queue’}], ‘users’: [{‘user_id’: ‘cFwgs3TgTZ2aq42iw3Esiw’, ‘user_name’: ‘Eleazar Gallegos’}], ‘events’: [{‘event_id’: ‘lz/usthbR3G/kfTbL4yRCw’, ‘event_name’: ‘engagement.start’}, {‘event_id’: ‘1TfYAlrXQYCIAyCQ/YZV8Q’, ‘event_name’: ‘customer.inbound.call’}, {‘event_id’: ‘qDTIxWndTwqmT3qNsVvqvw’, ‘event_name’: ‘flow.execution.start’}, {‘event_id’: ‘Qco61pU4Sx2Z1JtArVvzfA’, ‘event_name’: ‘flow.start.widget.start’},

…

‘transfer_completed_count’: 0, ‘warm_conference_count’: 0, ‘conference_count’: 0, ‘blocked’: False, ‘voicemail_count’: 0}]}

9

Hi @Orlando1
Thanks for reaching out to us
It seems like the List historical engagment log data endpoint does not support the from and to parameters.

It uses the start_time_from, start_time_to, end_time_from and end_time_to instead.

10

thank you! that worked.

1 Like