About the expiration of ”next_page_token”

API and Webhooks
1

Description
When I call the “meeting API” and the number of meetings is more than 300, I can get the next_page_token.
I know that the expiration time of the next_page_token is 15 minutes.
However, I saw a behavior that the next_page_token expires in 1 minute.
Have you changed the expiration time of next_page_token ?

Error
{
“code”: 300,
“message”: “The next page token is invalid or expired.”
}

Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT

Which Endpoint/s?
https://api.zoom.us/v2/metrics/meetings

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Request URL / Headers (without credentials) / Body
  2. See error

Screenshots (If applicable)
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

2

Hi @endo ,

Thank you for sharing this. Are you able to repeat this behavior?

Gianni

3

Hi @gianni.zoom , I am very sorry for the delay in replying.

It is difficult to reproduce this event.
I can’t attach an image of the log due to user level issues, so I’ll explain briefly

I have implemented a parallel call to Zoom’s meetingAPI. I set the time interval between calls to be 1 minute.
I could get the meeting information from page 1 to 5, but not from page 6 to 8.
Is it possible that the next_page_token is not available after 1 minute?

4

Hi @endo ,

This seems to be unexpected behavior. What we would need to look into this are the API call information such as the url with the meeting id, and the date/date-range in which you experienced this. Then I can see if there are any code 300 error responses to match what you’ve experienced and check the time in which each call was made. You can send that info to developersupport@zoom.us with a link to this thread.

Thank you,
Gianni

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.