# { "code": 300, "message": "The next page token is invalid or expired." }

**URL:** <https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029>\
**Category:** Meetings\
**Tags:** api\
**Created:** [November 18, 2022, 5:19pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029 "2022-11-18T17:19:26Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethanaaron](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanaaron/32/43146_2.png) [@ethanaaron](https://devforum.zoom.us/u/ethanaaron)\
**Post date:** [November 18, 2022, 5:19pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/1 "2022-11-18T17:19:26Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
Meeting participants endpoint - [Zoom Meeting API](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/reportMeetingParticipants)

**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/](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

---

<div class="post-metadata">

**Author:** ![ethanaaron](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanaaron/32/43146_2.png) [@ethanaaron](https://devforum.zoom.us/u/ethanaaron)\
**Post date:** [November 18, 2022, 5:47pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/2 "2022-11-18T17:47:48Z")

</div>

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 **must** [double encode](https://marketplace.zoom.us/docs/api-reference/using-zoom-apis/#meeting-id-and-uuid) 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.

---

<div class="post-metadata">

**Author:** ![ethanaaron](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanaaron/32/43146_2.png) [@ethanaaron](https://devforum.zoom.us/u/ethanaaron)\
**Post date:** [November 28, 2022, 4:30pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/3 "2022-11-28T16:30:25Z")

</div>

Any updates on this issue?

---

<div class="post-metadata">

**Author:** ![rarev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rarev/32/38939_2.png) [@rarev](https://devforum.zoom.us/u/rarev)\
**Post date:** [November 28, 2022, 9:08pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/4 "2022-11-28T21:08:49Z")

</div>

Hey @ethanaaron ,

I assume that you are also double encoding the UUID on the second request correct?

---

<div class="post-metadata">

**Author:** ![ethanaaron](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanaaron/32/43146_2.png) [@ethanaaron](https://devforum.zoom.us/u/ethanaaron)\
**Post date:** [November 28, 2022, 9:20pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/6 "2022-11-28T21:20:39Z")

</div>

Correct, we’re double encoding the UUID for both requests. The request URLs are identical, the query parameters are the only difference.

---

<div class="post-metadata">

**Author:** ![rarev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rarev/32/38939_2.png) [@rarev](https://devforum.zoom.us/u/rarev)\
**Post date:** [November 28, 2022, 10:42pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/7 "2022-11-28T22:42:48Z")

</div>

@ethanaaron

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.

---

<div class="post-metadata">

**Author:** ![ethanaaron](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanaaron/32/43146_2.png) [@ethanaaron](https://devforum.zoom.us/u/ethanaaron)\
**Post date:** [November 29, 2022, 7:53pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/8 "2022-11-29T19:53:27Z")

</div>

The subsequent request is within ~ 1 minute of the initial request.

The query parameters and headers are included in the requests.

Is there someone I can speak with to troubleshoot this? Would love to get this resolved quickly.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [December 5, 2022, 10:12pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/9 "2022-12-05T22:12:06Z")

</div>

Hi @ethanaaron  
Were you able to troubleshoot this issue?

---

<div class="post-metadata">

**Author:** ![ethanaaron](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanaaron/32/43146_2.png) [@ethanaaron](https://devforum.zoom.us/u/ethanaaron)\
**Post date:** [December 12, 2022, 12:44am UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/10 "2022-12-12T00:44:12Z")

</div>

@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?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [December 21, 2022, 6:39pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/11 "2022-12-21T18:39:13Z")

</div>

I have sent you a DM @ethanaaron  
I will take it from there

---

<div class="post-metadata">

**Author:** ![salari.m.amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/salari.m.amir/32/51849_2.png) [@salari.m.amir](https://devforum.zoom.us/u/salari.m.amir)\
**Post date:** [April 3, 2024, 5:00pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/12 "2024-04-03T17:00:26Z")

</div>

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).

Did you find any solution for that? @ethanaaron @elisa.zoom

Thanks!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [June 28, 2024, 4:08pm UTC](https://devforum.zoom.us/t/code-300-message-the-next-page-token-is-invalid-or-expired/79029/13 "2024-06-28T16:08:55Z")

</div>

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
