Login API errors
In case of error responses the Xsolla Login server returns a JSON object with the following fields:
| Field | Type | Description |
|---|---|---|
| code | string | Xsolla Login server error code. |
| description | string | Error description. The text is always in English. Do not use this text in case of an error, as the value can change in the future. |
Copy
1{
2 "error": {
3 "code": "000-000",
4 "description": "description"
5 }
6}
| Code | Description | Troubleshooting |
|---|---|---|
| 002-016 | Invalid JWT. | The user should try to log in again. |
| 002-027 | Parameter is invalid. | Make sure all request parameters are correct. |
| 002-028 | Parameter was not passed. | Make sure all required parameters are provided. |
| 002-040 | This user is banned. | The user should contact the game support team. |
| 002-043 | This phone number cannot receive SMS. Use a different number. | The user should try another phone number that can receive SMS. |
| 002-050 | User MFA settings have not changed. | The error occurs when trying to enable two-factor authentication if it’s already enabled, or disable it if it’s already disabled. |
| 002-056 | Invalid phone number. Verify the number or try another one. | The user should verify the phone number or enter a different one. |
| 002-057 | Too many login attempts. | The user should try again later. If you believe this error should not occur, please contact the integrator team in any messenger. |
| 002-058 | You exceeded login attempts limit. To unblock your account, follow the link in the email that we sent or reset your password. | The user should use the link in the email to unblock their account or reset the password. |
| 002-060 | User younger than required age. | Inform the user of the age restrictions. |
| 003-001 | Incorrect email address/username or password. | The user should verify the entered information and try again. |
| 003-002 | User is not signed up. | The user should sign up in the game to continue. |
| 003-003 | User with this username already exists. Try another username. | The user should try a different username. |
| 003-004 | User with this email address already exists. Try another email address. | The user should use a different email address. |
| 003-005 | Email address does not exist. Try another email address. | The user should try a different email address. |
| 003-007 | Account not activated. Please confirm email address. | The user should confirm their email address to activate the account. If they haven’t received a confirmation email, they should check the spam folder. |
| 003-008 | Changing email address not allowed. | Changing the email address is not allowed. |
| 003-009 | User search request wrong. | The search failed for technical reasons, please try again later. |
| 003-010 | Changing birth date is unavailable. | Changing the birth date is not allowed. |
| 003-011 | Email address not confirmed. Try another email address or confirm this one. | The user should confirm the email address or use another one that has not been previously used during registration. |
| 003-012 | User with specified phone number already exists. | The user should confirm the phone number or use another one that has not been previously used during registration. |
| 003-019 | Login with this project ID not found. | Check the existence of the authentication variant with the passed ID. |
| 003-020 | Call unavailable for this Login project. | Check the authorization option settings in your Publisher Account. |
| 003-021 | Logging in via username/password not allowed. | The user should contact game support. |
| 003-022 | Incorrect project configuration. | Verify the authorization option settings in your Publisher Account. |
| 003-023 | Signing up via username/password not allowed. | Registration is not allowed for this authorization option. The user should contact game support. |
| 003-030 | Link has expired. Please perform password recovery again. | The password reset link has expired or is incorrect. The user should attempt to reset the password again. |
| 003-049 | Too many attempts to use confirmation code. Try again later. | The user should try again later. |
| 007-001 | Login via phone is currently unavailable in your country. Please try a different login method. | The user should use an alternative login method. |
| 008-001 | Passwordless login URL not configured. | Add the correct login URL in the authorization option settings in your Publisher Account (User database > Storage > Custom storage section). |
| 008-002 | User verification URL not configured. | Add the correct user verification URL in the authorization option settings in your Publisher Account (User database > Storage > Custom storage section). |
| 008-003 | New user URL not configured. | Add the correct URL in the authorization option settings in your Publisher Account (User database > Storage > Custom storage section). |
| 008-004 | Password reset URL not configured. | Add the correct password reset URL in the authorization option settings in your Publisher Account (User database > Storage > Custom storage section). |
| 008-005 | PlayFab Title ID invalid. | Ensure the correct Title ID is specified in the authorization option settings in your Publisher Account (User database > Storage section). |
| 008-006 | PlayFab API key invalid. | Ensure the PlayFab API key is valid. |
| 008-008 | Invalid response from your API. It must contain user ID as “accountID” response body parameter. | Ensure the server returns the accountID parameter in the response body. |
| 008-009 | Invalid URL in Custom storage settings. | Verify the URLs specified in the Custom storage settings in the authorization option in your Publisher Account (User database > Storage > Custom storage section). |
| 008-011 | Set new password page URL not configured. | Ensure that the callback URL for password reset is specified in the authorization option settings in your Publisher Account (Password settings section). |
| 008-013 | Consent page URL not configured or invalid. | Ensure that a link to the user agreement is specified in the authorization option settings in your Publisher Account (Legal Terms > Policies and Agreements section). |
| 008-014 | Okta integration not completed. | Contact the integration team through any messenger. |
| 008-015 | SAML integration not completed. | Contact the integration team through any messenger. |
| 008-016 | Firebase API key not set. | Add the API key to the settings in your Publisher Account (section Legal Terms > Policies and Agreements). |
| 010-004 | Service temporarily unavailable. Try again later. | The user should try again later. |
| 010-005 | Allowable number of requests exceeded. Try again later. | The user should try again later. |
| 010-006 | If this social profile is unlinked, no authentication methods will be available. | The user should add another authentication method before unlinking the social network. |
| 010-007 | Incorrect CAPTCHA input. Try again. | The user should complete the CAPTCHA again. |
| 010-010 | Invalid confirmation code. | The user should verify the code and try again. |
| 010-014 | Your code is expired. Return to the login page and log in again. | The user should log in again from the login page. |
| 010-015 | Something went wrong during authentication with this social network. Try again later. | The user should try again later. |
| 010-016 | This social account is already linked to another user. | The user should use a different social account. If they believe this is an error, they should contact the integration team through any messenger. |
| 010-017 | Client authentication failed. Some request parameters are missing in request or have invalid values. | Verify the correctness of the request parameters being sent. |
| 010-019 | Client authentication failed. Client with this client_id value does not exist. | Ensure that a client with the provided client ID exists. |
| 010-020 | Client authentication failed. Parameter scope is invalid or malformed. | Ensure that the provided scope parameter is correct. Refer to the instructions for detailed setup information. |
| 010-021 | Client authentication failed. Parameter response_type is invalid or malformed. You should pass value of code parameter to response_type. | Ensure that the value of the response_type parameter is set to code. |
| 010-022 | Client authentication failed. Parameter state is missing or its value has less than 8 characters. | Ensure that the state parameter is present and consists of at least 8 characters. |
| 010-023 | Client authentication failed. Authorization code, authorization grant types, or refresh token are invalid or expired. Also this error is returned when the redirect_uri given in authorization grant type does not match the URI provided in access token request. | Ensure that the authorization code is valid and not expired, and that the redirect_uri parameter contains an authorized URL. Refer to the instructions for detailed setup information. |
| 010-026 | The resource owner or authorization server denied the request. | Ensure that you have sufficient permissions to access the resource. |
| 010-030 | Cross social network is not enabled for this Login. | Ensure that cross-authentication is enabled for the authorization option. Refer to the instructions for detailed setup information. |
| 010-031 | Social provider already exists. | The error occurs when attempting to connecta social network that is already enabled. |
| 010-032 | Social network is not enabled for this Login. You can enable it in your Xsolla Publisher Account > Login Project > Social connections. | Ensure that the social network is enabled and configured in the authorization option settings in your Publisher Account (Authorization via Social Networks section). |
| 010-033 | This call is temporary unavailable. | The user should try again later. |
| 010-035 | Dependency service is unavailable | The user should try again later. |
| 010-045 | Account with this social provider email address already exists. | The user should use a different social account for registration. |
| 030-024 | Password recovery is not allowed. | The user should contact the game support team. |
| 040-001 | Email address must be 254 characters or shorter. | The user should enter an email address containing no more than 254 characters. |
| 040-002 | Username of the email address is invalid. Try another email address. | The user should enter a valid email address. |
| 040-003 | Local part of the email address is too long. | The user should enter a different email address. |
| 040-004 | Email address domain is invalid. Try another email address. | The user should contact Xsolla support. |
| 040-005 | Email address should contain one @ character only. (E.g., username@example.com) | The user should enter an email with only one @ character. |
| 040-006, 040-007, 040-008 | Email address domain is invalid. Try another email address. | The user should contact Xsolla support. |
| 040-009 | Email address domain doesn’t exist. Try another email address. | The user should enter an email with an existing domain. |
| 040-010 | Email address domain is not allowed. Try another email address. | The user should contact Xsolla support. |
| 010-018 | Email address is invalid. Try another email address. | The user should enter a different email address. |
| 300-003 | Allowable number of requests exceeded. Try again later. | The user should try again later. |
| 300-005 | Failed to resend code. Try again later. | The user should try again later. |
| 300-006 | Incorrect confirmation code. Check the code that you received and try again. | The user should verify and re-enter the confirmation code. |
| 300-008 | You’ve exceeded the maximum number of attempts. Use the new code sent to your email or phone. | The user should use the new code sent to their email or phone. |
| 003-007 | User account not confirmed. | The user should confirm their email address to activate the account. If they haven’t received a confirmation email, they should check the spam folder. |
| 003-025 | Error occurred while getting OAuth 2.0 access token. | The user should try a different authentication method. |
| 003-040 | Unauthorized user. | The user should log in again. |
| 003-033 | Mismatch project type. | Ensure that shadow authentication is used for the authorization option. |
| 2002-0001 | Duplicated attributes. | Make sure that the attribute being created has not been previously added to the user. |
Was this article helpful?
Thank you for your feedback!
We’ll review your message and use it to help us improve your experience.Found a typo or other text error? Select the text and press Ctrl+Enter.
