Using this template helps us debug your issues more effectively
Description
I was loading the meetings and then gathering the participant for each meeting one at a time. Running into the 400 error.
And I totally disagree with below ticket.
Because, I have seen List of Meetings (without participants) ran for more than 9 hours (without 400 Bad Request). Means, the time difference between initial request and final request is 9 hours and 30 minutes.
Error
“code”:400,“message”:“400 Bad Request”,“body”:“{"code":300,"message":"The next page token is invalid or expired."}”
Thank you for using the Zoom Developer Forum. Are you able to share an example where the time difference between initial request and final request exceeds the next_page_token expiration period ?
This information will help to diagnose what may be happening.
Hi Donte,
I am afraid, that you misunderstood my words.
In one of your previous Zoom Dev Forum ticket (copied link), it was said that if pagination request is issued after 15 minutes from your first request, this issue will happen.
For this, I have clarified, I have seen time difference between first request and last request was almost 9.5 hours and still it worked fine for me. For same from and to, it works one time (time taken 43 minutes) , fails one time.
Here is my example.
m_next_page_token= null;
do
{
res = List meetings (limit: 300, next_page_token: {m_next_page_token});
m_next_page_token = res.next_page_token;
For each meeting
{
mp_next_page_token = null;
do
{
mp_res = Get List Participants (meeting_id: {meeting_id} , limit: 300, next_page_token: {mp_next_page_token});
mp_next_page_token = mp_res.next_page_token;
}while(!mp_next_page_token);
}
}while(!m_next_page_token);
Can you share the exact request URL you used, including the params and their values? Please confirm the approximate timestamp of the request as well—we can take a closer look and check our logs for more details.