# Refresh Tokens are Always Invalid

**URL:** <https://devforum.zoom.us/t/refresh-tokens-are-always-invalid/40702>\
**Category:** API and Webhooks\
**Created:** [January 15, 2021, 6:36pm UTC](https://devforum.zoom.us/t/refresh-tokens-are-always-invalid/40702 "2021-01-15T18:36:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattexware](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@mattexware](https://devforum.zoom.us/u/mattexware)\
**Post date:** [January 15, 2021, 6:36pm UTC](https://devforum.zoom.us/t/refresh-tokens-are-always-invalid/40702/1 "2021-01-15T18:36:31Z")

</div>

**Description**  
When I request a new access token (and refresh token) the refresh token is always invalid. The access token works perfectly fine.

I know that the refresh token changes after the first refresh but the first refresh always fails.

POST to [https://zoom.us/oauth/token?grant\_type=refresh\_token&refresh\_token=[[refresh\_token]](https://zoom.us/oauth/token?grant_type=refresh_token&refresh_token=%5B%5Brefresh_token%5D)]

**Error**  
HTTP/1.1 401 Unauthorized  
Cache-Control: no-store  
Connection: close  
Date: Fri, 15 Jan 2021 18:23:22 GMT  
Pragma: no-cache  
Server: nginx  
Content-Type: application/json;charset=UTF-8  
Client-Date: Fri, 15 Jan 2021 18:23:22 GMT  
Client-Peer: \*\*\*\*  
Client-Response-Num: 1  
Client-SSL-Cert-Issuer: /C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA  
Client-SSL-Cert-Subject: /C=US/ST=California/L=San Jose/O=Zoom Video Communications, Inc./CN=\*.zoom.us  
Client-SSL-Cipher: ECDHE-RSA-AES256-GCM-SHA384  
Client-SSL-Warning: Peer certificate not verified  
Client-Transfer-Encoding: chunked  
Client-Warning: Missing Authenticate header  
Content-Security-Policy: upgrade-insecure-requests; …’;

{“reason”:“Invalid Token!”,“error”:“invalid\_request”}

My current refresh token:  
eyJhbGciOiJIUzUxMiIsInYiOiIyLjAiLCJraWQiOiJlOTUwZTBlNy0yYTZhLTQxYzYtOWRkYi1hZjYzZmI4ZDU1MGEifQ.eyJ2ZXIiOjcsImF1aWQiOiJkMDg2ZDU2MjIyN2E1MjM3M2UxNDRmZjNjODQ3Zjk4YyIsImNvZGUiOiJLYmlxZDJMTUNTX0JKUlZoTjV0VGxlZjhISFBWcm9CRHciLCJpc3MiOiJ6bTpjaWQ6OUozQ3g3dEJTZzJlTk13ak9aV21qUSIsImdubyI6MCwidHlwZSI6MSwidGlkIjowLCJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJCSlJWaE41dFRsZWY4SEhQVnJvQkR3IiwibmJmIjoxNjEwNzM0NDQyLCJleHAiOjIwODM3NzQ0NDIsImlhdCI6MTYxMDczNDQ0MiwiYWlkIjoiMzNSZk4xTDBTdWlxdklZOXpjcFhmdyIsImp0aSI6ImExNWNiOTAzLTUyNzUtNGM1Yy04ZGU2LTE0OTI3YzAzOWM3NyJ9.OlvGRc5vCYWBYzsia7z7BocRRcsoigUdrdnW0GAapy2dE2cpgdcIqlHIixdaqBkfMl03oqnis3kna1jOX7ow2Q

Tried it in Postman and it gives the same error.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [January 19, 2021, 4:39pm UTC](https://devforum.zoom.us/t/refresh-tokens-are-always-invalid/40702/2 "2021-01-19T16:39:28Z")

</div>

Hi @mattexware,

Thanks for reaching out about this.

Can you please ensure that you’re using the most up to date refresh token? Please note that each time an access token is retrieved, both the access\_token and refresh\_token are refreshed, invalidating the previous refresh token.

Additionally, please ensure that you’re passing an Authorization header:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/a/2/a27589743ec7efb4e686a3cdf7b8fdb788b523a1.png)

Let me know if this helps,  
Will

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [February 19, 2021, 2:39am UTC](https://devforum.zoom.us/t/refresh-tokens-are-always-invalid/40702/3 "2021-02-19T02:39:30Z")

</div>

Closed on February 19, 2021, 2:39am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
