API Endpoint(s) and/or Zoom API Event(s)
Meeting participants endpoint - Zoom Meeting API
Description
When we make the first call to the meeting participants endpoint, it works fine. When we make the second call using the next_page_token from the first response, we get the error message “The next page token is invalid or expired.”
Error?
{ “code”: 300, “message”: “The next page token is invalid or expired.” }
How To Reproduce
This API call works:
URL: “https://api.zoom.us/v2/report/meetings/{{ double url encoded meeting instance id }}/participants”
Query Parameters: “page_size”: “300”
Headers: N/A
This API call doesn’t work (i.e. the second page of data):
URL: The same URL as the first call
Query Parameters: “next_page_token”: “{{ token from prior call’s response }}”, “page_size”: “300”
Headers: N/A
Specifically, it appears to only be happening when the meeting instance ID has forward slashes in it.
The Zoom documentation says that these UUIDs should be double URL encoded.
** If you provide a meeting UUID that begins with a / character or contains the // characters, you mustdouble encode the meeting UUID before making an API request.*
That works for the first request, but on the second request the next_page_token is throwing the errors above.
In your subsequent request, it’s within 15 minutes of the initial one correct? I’m not really sure why this would be happening.
When you make the request, do you see that the headers are indeed all there, and that the query params are being passed to the request.
This endpoint doesn’t have many parameters so I’m not really sure what could be happening here other than perhaps the query string is empty for some reason.
@elisa.zoom - No, I wasn’t able to troubleshoot the issue. I haven’t yet been put in touch with anyone at Zoom that can help. Is there someone I can speak with to troubleshoot / get this resolved?
Hi, I also have this problem. The participant endpoint only works for non-recurring meetings, as recurring meetings have the same ID. For the second and subsequent occurrences, the endpoint throws an error stating that the next page token is expired or invalid (the next page token is actually None).
Hi @salari.m.amir
Thanks for reaching out! This post is very old, if you are still experiencing this issue please open up a new thread and describe the issue you are having so we can take a closer look
Cheers
Elisa