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.

proxy_oauth_failed

If you receive a 502 Bad Gateway response when hitting an API endpoint, your response body may look like:

{
  "error": "proxy_oauth_failed",
  "detail": "Error: oauth_400:invalid_request: The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. Requested audience '<your audience>' has not been whitelisted by the Auth 2.0 Client."
}

This is caused by an incorrect value for the audience parameter. The audience parameter must be set to urn:partner-api.

Last Updated: Jul 28th, 2025

On this page