# Auth problem in meeting instances request with s2s auth

**URL:** <https://devforum.zoom.us/t/auth-problem-in-meeting-instances-request-with-s2s-auth/87957>\
**Category:** Meetings\
**Tags:** server-to-server\
**Created:** [May 7, 2023, 11:22pm UTC](https://devforum.zoom.us/t/auth-problem-in-meeting-instances-request-with-s2s-auth/87957 "2023-05-07T23:22:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anreta](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@anreta](https://devforum.zoom.us/u/anreta)\
**Post date:** [May 7, 2023, 11:22pm UTC](https://devforum.zoom.us/t/auth-problem-in-meeting-instances-request-with-s2s-auth/87957/1 "2023-05-07T23:22:37Z")

</div>

Hi,  
I am getting authorization problems in ‘List past meeting instances’ request with the S2S token.

I added Scopes: `meeting:read:admin` , `meeting:read`. When the error did not fix, I activated all the scopes, but it still did not fix.

The interesting thing is it works on 1 out of 5 requests.

I don’t have a problem when I test with jwt token.

---

<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:** [May 8, 2023, 8:12pm UTC](https://devforum.zoom.us/t/auth-problem-in-meeting-instances-request-with-s2s-auth/87957/2 "2023-05-08T20:12:27Z")

</div>

Hi @anreta  
Thanks for reaching out to us, I am happy to help here!  
Can you please make sure that the token is not being invalidated by the creation of a new one?

When you generate a token with your Server-to-Server OAuth app credentials this will have an expiration time of 1 hour, but if you create a new token the previous one will get invalidated even if it has not expired yet.

Hope this helps,  
Elisa

---

<div class="post-metadata">

**Author:** ![anreta](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@anreta](https://devforum.zoom.us/u/anreta)\
**Post date:** [May 11, 2023, 11:07pm UTC](https://devforum.zoom.us/t/auth-problem-in-meeting-instances-request-with-s2s-auth/87957/3 "2023-05-11T23:07:17Z")

</div>

> [@elisa.zoom](#):
>
> When you generate a token with your Server-to-Server OAuth app credentials this will have an expiration time of 1 hour, but if you create a new token the previous one will get invalidated even if it has not expired yet.

Yes I used valid token.

I’m using the same code with jwt and I’m not getting any error, but I’m having trouble with S2S.

---

<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:** [May 12, 2023, 1:22pm UTC](https://devforum.zoom.us/t/auth-problem-in-meeting-instances-request-with-s2s-auth/87957/4 "2023-05-12T13:22:27Z")

</div>

So @anreta  
could you confirm that you can use a token generated with our Server to Server oauth app but only 1 or 2 times and then it stops working?
