We’ve been seeing the same error on our production systems, intermittently. We have many customers creating thousands of Zoom meetings, but rarely (several times a month at our scale), when we fetch a new refresh token, we get this error with status code 400:
{
“reason”: “Invalid Token!”,
“error”: “invalid_grant”
}
This user reported a similar issue but the error was “invalid_request” and the status code was 401: ZOOM API refresh token not working {"reason":"Invalid Token!","error":"invalid_request"}
It seems similar to this error, which is basically a race condition: Intermittent 400 error when refreshing token "Save Access token into Database error"
Can your engineers provide insight into the 400 invalid_grant Invalid Token! error? It seems to be a bug in Zoom’s API.
I suspect that this is just another race condition (ie we are using the same refresh token to fetch a new refresh token twice, very quickly). But it would be nice to know what the error means for sure.
When this happens, the next request typically goes through without problem, so there is definitely nothing wrong with the credentials.