Error Handling

Web Server Applications and Installed Applications that implement the Authorization Code grant type to first request an Authorization Code may instead receive an error in the callback, as follows:

<REDIRECT_URUL>?error=<ERROR_CODE>

Here is an example:

https://myapp.com/oauth/callback?error=invalid_client

Any HTTP GET or POST may return Status Code 400 or 401 and a response Body, as follows:

{
  "error": <ERROR_CODE>,
  "error_description": <ERROR_DESCRIPTION>
}

Here is an example:

{
  "error":"invalid_grant",
  "error_description":"Audience validation failed"
}

Authorization code flow error codes:

Error Code	Error Description
invalid_redirect_uri	Client <client-id> specified an invalid redirect URL: <callback-url>
invalid_client	Client authentication failed.
invalid_request	Possible descriptions, depending on the cause: The request contains invalid parameters or values. Invalid PKCE code_challenge_verifier. PKCE is mandatory for public clients.
aconex_account_not_found	No linked Aconex account found.

Oauth token generation API error codes:

Error Code	Error Description
invalid_request	Possible descriptions, depending on the cause: Invalid or missing grant_type. Invalid or missing user_site. Invalid Aconex account. Invalid user assertion. Client authentication failed.
invalid_token_or_code	Possible descriptions, depending on the cause: Invalid or expired authorization code. Invalid or expired refresh token.
invalid_auth_header	Client authentication failed.
invalid_aconex_account	Possible descriptions, depending on the cause: Aconex account not specified. Invalid Aconex account.
unauthorized_client	Client not authorized for requested Aconex account.
invalid_redirect_uri	Invalid redirect URL: <redirect-url>
invalid_amr_claims	AMR claims validation failed.
failed_to_process_error_response	Internal processing error.
failed_to_process_request	Unexpected system error.