OAuth 2.0 Errors¶
Refer to the following error codes and explanations when troubleshooting OAuth 2.0 errors:
400 Errors¶
A 400 Error indicates that a request is invalid. You omitted a required parameter or Yahoo couldn’t make sense of a parameter you supplied.
Error |
Description |
---|---|
|
OAuth 2.0 only supports calls over HTTPS. |
|
An unsupported version of OAuth was supplied. |
|
A required parameter is missing from the request. |
|
A provided parameter is too long. |
|
An invalid Client ID was provided. |
|
An invalid request parameter was provided. |
|
The provided |
|
The provided |
|
The provided |
|
The provided |
|
A provided request parameter is invalid. |
|
The provided refresh token is invalid. |
401 Errors¶
A 401 error indicates that the authorization information for a request is absent or invalid.
Error |
Description |
---|---|
|
The provided refresh token has expired. |
|
The |
|
The user who must authorize access is a minor and cannot authorize access. |
|
An invalid Client Secret was provided. |
|
An invalid or expired token was provided. |
403 Errors¶
A 403 error indicates that request is forbidden.
Error |
Description |
---|---|
|
The user has not authorized requesting Client ID (Consumer Key). |
Authorization Errors¶
The following errors presented on the browser when user authorizes the app.
INTERNAL_ERROR
INVALID_CONSUMER_KEY
DELETED_CONSUMER_KEY
DISABLED_CONSUMER_KEY
INVALID_TOKEN
EXPIRED_TOKEN
INVALID_CALLBACK_URL
INVALID_SCOPE
UNSUPPORTED_OVER_HTTP
,UNDERAGE_USER
PARAMS_MAXLENGTH_EXCEEDED
BAD_REDIRECT_URI
INVALID_RESPONSE_TYPE
INVALID_REQUEST
PARAM_TOO_LONG