# Error when get call\_logs {"code":401,"message":"The account access token is invalid"} **URL:** \ **Category:** Phone\ **Created:** [October 17, 2022, 4:40pm UTC](https://devforum.zoom.us/t/error-when-get-call-logs-code-401-message-the-account-access-token-is-invalid/77503 "2022-10-17T16:40:12Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![david5](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david5/32/40553_2.png) [@david5](https://devforum.zoom.us/u/david5)\ **Post date:** [October 19, 2022, 1:24pm UTC](https://devforum.zoom.us/t/error-when-get-call-logs-code-401-message-the-account-access-token-is-invalid/77503/3 "2022-10-19T13:24:07Z")
I suspect you’re hitting the same “feature” we did, where another service/host is requesting a new Server-to-Server OAuth token and invalidating the one you are using in this particular instance: > [@Randomly receiving "Invalid access token" for Server-to-Server OAuth](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432/22): > > For posterity and anyone else who happens to run across this thread while scratching their head about how Server-to-Server OAuth works: Requesting a new Server-to-Server OAuth token invalidates the previous one. Zoom can increase the “index” count for your account, allowing you to request different tokens with different indexes that do not interfere with each other (i.e. requesting a token for index 1 doesn’t invalidate the token requested for index 2). The token index is specified in the call… --- _[View the full topic](https://devforum.zoom.us/t/error-when-get-call-logs-code-401-message-the-account-access-token-is-invalid/77503)._