I’ve been successfully working with the API for a few days now, but just started getting this 401 today:
the token id 2is outside of the token tolerance offset 0. The current id is 0
How can I resolve this?
I’ve noticed that each time I exchange a refresh token for new tokens, the “token id” (in this case 2) increments in the error message, so I have a feeling it may have to do something with that, but I’m not sure what to do to avoid this issue.
Thanks in advance!
Full HTTP Request & Response
(I redacted the bearer token and cookie out of habit, but let me know if providing those would help.)
REQUEST
GET https://api.zoom.us/v2/users/me/recordings?from=2018-05-22+17%3A08%3A49+UTC&page_size=300
HEADERS: {"Content-Type"=>"application/json", "Authorization"=>"Bearer [REDACTED]", "User-Agent"=>"Faraday v0.15.4"}
BODY: [NO REQUEST BODY]
RESPONSE
STATUS: 401
HEADERS: {"Date"=>"Wed, 22 May 2019 17:08:49 GMT", "Content-Type"=>"application/json;charset=UTF-8", "Transfer-Encoding"=>"chunked", "Connection"=>"keep-alive", "Server"=>"ZOOM", "x-zm-trackingid"=>"WEB_3c9d5e627c0e71eb0793c5bb717b5d30", "Set-Cookie"=>"[REDACTED]"}
BODY: {"code":124,"message":"the token id 2is outside of the token tolerance offset 0. The current id is 0"}
@TimZoom Error is the same even after rolling the client secret. The number in the error message increments each time I exchange a refresh token, so I believe it has something to do with the refresh and/or bearer tokens. Any other ideas for me to try?