Troubleshooting

Discover solutions to commonly encountered questions when Getting Started.

invalid_client

If you receive a 401 Unauthorized response when hitting the /oauth2/token endpoint, your response body may look like:

{
  "error": "invalid_client",
  "error_description": "Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method)."
}

This is due to a Client not being found in the associated Environment's OAuth Authorization Server. To resolve this, ensure that you are using the correct OAuth Authorization Server, clientID, and clientSecret for the desired Environment.

token is not active

If you receive a 401 Unauthorized response when hitting an API endpoint, your response body may look like:

{
  "type": "about:blank",
  "title": "Unauthorized",
  "status": 401,
  "detail": "invalid token. failure reason(s): [token is not active]"
}

This is due to your access_token having expired. Be sure you utilize an OAuth2 library or the OAuth2 functionality of your API Client to handle refreshing for you.

On this page

Troubleshooting

invalid_client

token is not active