Zoom call_history bug, returns next_page_token when it should

API and Webhooks
1

The call_history API calls return next_page_token when it should not be.

Example: API call with 39 records total, using page size=20

First API call returns:

“next_page_token”: “tcH6pER2BpRTFhLFTmyJjsH7WvlzKI1w6A2”,
“page_count”: 2,
“page_size”: 20,
“total_records”: 39,
“from”: “2024-11-26T01:38:48Z”,
“to”: “2024-11-26T06:48:50Z”,
“call_logs”: […call data array]

Second API Call returns:

“next_page_token”: “qHTEYKjo62s0hrygUS0VTRamrXe9hlp8cm2”,
“page_count”: 2,
“page_size”: 20,
“total_records”: 39,
“from”: “2024-11-26T01:38:48Z”,
“to”: “2024-11-26T06:48:50Z”,
“call_logs”: […call data array]

Note that the total records is 39 and I’ve already retrieved all 39 records, so there should not be a need to make an additional API call. Page size of 20 * 2 API calls = 40 records. 39 record in total, so there is no additional page needed.

In the second API call, the next_page_token should be empty.

The 3rd API Call returns:

"next_page_token": **"",**
"page_count": 2,
"page_size": 20,
"total_records": 39,
"from": "2024-11-26T01:38:48Z",
"to": "2024-11-26T06:48:50Z",
"call_logs": []

This is causing Zoom to require people to make more API calls than are necessary. I’m not sure how to report this as a bug, but figured someone here can provide guidance.

2

Hi @davidrrobinson
Thanks for bringing this to our attention.
As I don’t have enough data to test this, would you mind sharing the response data you are getting so I can share this with my team?
If so, please follow up in the DM that I just sent.
Cheers,
Elisa

3

Sure, see the PM. The results were posted above except for the call_logs array that was returned.