Description: Oftentimes, we might run into a response error of INVALID_TOKEN
with a message stating the Token is not valid when we are sending a request to an API.
The following might be one of the reasons why we see the issue,
-
The API Key may no longer exist. To check and see if the API key exists, For First Gen, you can view it under Security → Access Management → API Keys and for Next Gen, My Profile → My API Keys
-
The API Key is incompatible with the API endpoint you send a request to. The API key created for First Gen is only compatible with accessing the First Gen REST API and the same with Next Gen.
-
The API Key might have reached it TTL for the token generated under a given service account.