We are trying to import information from the Zoom REST APIs, and we have successfully done this for many endpoints. However, we are encountering issues when importing data from the voice_calls endpoint, specifically when the number of pages exceeds 100.
We were unable to find any information regarding a limit on the number of pages, but we wanted to reach out to confirm.
Is there a limitation on the number of pages that can be retrieved from a REST API endpoint? We are currently fetching 100 objects per page, for a total of 10,000 elements.
I want to add another anomaly to docs/api/phone/#tag/voicemails/GET/phone/voice_mails
When executing
/contact_center/voice_calls?page_size=100&from=2024-07-01T00:00:00Z&to=2024-07-31T23:59:59Z
We get:
“total_records”: 74117,
“from”: “2024-07-01T00:00:00Z”,
“to”: “2024-07-31T23:59:59Z”,
But when executing the days separately, let’s say
/contact_center/voice_calls?page_size=100&from=2024-07-01T00:00:00Z&to=2024-07-01T23:59:59Z
/contact_center/voice_calls?page_size=100&from=2024-07-02T00:00:00Z&to=2024-07-02T23:59:59Z
…
/contact_center/voice_calls?page_size=100&from=2024-07-31T00:00:00Z&to=2024-07-31T23:59:59Z
We get a total of 74296 records which is more than the original number 74117.
We found part of the issue. It seems the endpoint only displays completed calls.
So, if we capture the time range from 00:00:00 to 23:59:59 on a specific day, we might be missing calls that finished the next day.
Would this be correct? This is not super clear in the documentation.
Since these REST APIs are mainly for reporting, it becomes really difficult to incrementally load information from the endpoints due to this behavior.
We have added a sliding window to our logic, but it would be much better to use the ‘from’ and ‘to’ parameters to filter the end_time column of the endpoints for completed calls, rather than relying on calls that finished within a specific period of time.
You are right, I misread the message
I created an internal ticket about this (ZSEE-153439 internal number for reference). I will update you when I have more information about it
Hi @dalzamendi
I just heard back from our Engineering team, and they identified the root cause and we will enhance it. I will keep you updated on the fix for this once I have more information