# Reset password

Resets the user password with user confirmation. If the user data is kept in the Xsolla data storage or on your side, users receive a password change confirmation email. If the user data is kept in the PlayFab storage, password reset is done on PlayFab’s side. To get more information, see the Comparison of user data storages page.

The workflow of using this call:
1. The application opens a form so the user can enter their email or username.
2. The user enters their email or username.
3. The application sends this request to the Xsolla Login server.
4. The Xsolla Login server sends a confirmation email to the user.
5. The user follows the link in the email and proceeds to the form for setting a new password.
6. The user enters a new password and clicks Set new password.
7. The application sends the Confirm password reset request to the Xsolla Login server.

If you use your own password reset form, use the Confirm password reset call to reset the user password.

Endpoint: POST /password/reset/request
Version: v1

## Query parameters:

  - `projectId` (string, required)
    Login project ID from Publisher Account.

  - `login_url` (string)
    URL to redirect the user to after account confirmation, successful authentication, two-factor authentication configuration, or password reset confirmation. Must be identical to the Callback URL specified in the URL block of Publisher Account. For the scenario of a login error, the value should be identical to the the Error callback URL specified in the URL block of Publisher Account. To find the settings, go to Login > your Login project and select the Callback URLs section in the upper block. Required if there are several Callback URLs.

  - `locale` (string)
    Region in the _ format, where:

* language code: language code in the ISO 639-1 format;
* country code: country/region code in the ISO 3166-1 alpha-2 format.

The list of social networks will be sorted from most to least used, according to the variable value.

## Request fields (application/json):

  - `username` (string, required)
    Email to send the password change verification message to.
    Example: "John"

## Response 400 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 401 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 404 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 422 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 429 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.


## Response 204 fields