> For the complete documentation index, see [llms.txt](https://painor.gitbook.io/gramjs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://painor.gitbook.io/gramjs/working-with-2fa-login/account.updatepasswordsettings.md).

# account.updatePasswordSettings

Set a new 2FA password

## Example

{% tabs %}
{% tab title="Javascript" %}

```javascript
const {Api, TelegramClient} = require('telegram');
const {StringSession} = require('telegram/sessions');

const session = new StringSession('');
const client = new TelegramClient(session, apiId, apiHash, {});

(async function run() {
    const result = await client.invoke(new Api.account.updatePasswordSettings({
        password: new Api.InputCheckPasswordSRP({...}),
        newSettings: new Api.account.PasswordInputSettings({...}),
        }));
    console.log(result); // prints the result
})();
```

{% endtab %}

{% tab title="TypeScript" %}

```typescript
import {Api, TelegramClient} from 'telegram';
import {StringSession} from 'telegram/sessions';

const session = new StringSession('');
const client = new TelegramClient(session, apiId, apiHash, {});

(async function run() {
    const result: Api.Bool = await client.invoke(new Api.account.updatePasswordSettings({
        password: new Api.InputCheckPasswordSRP({...}),
        newSettings: new Api.account.PasswordInputSettings({...}),
        }));
    console.log(result); // prints the result
})();
```

{% endtab %}
{% endtabs %}

## TL schema

```
boolFalse#bc799737 = Bool;
boolTrue#997275b5 = Bool;
---functions---
account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
```

## Parameters

|        Name       | Type                                                                                          | Description                                                     |
| :---------------: | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
|    **password**   | [InputCheckPasswordSRP](https://core.telegram.org/type/InputCheckPasswordSRP)                 | The old password (see [SRP](https://core.telegram.org/api/srp)) |
| **new\_settings** | [account.PasswordInputSettings](https://core.telegram.org/type/account.PasswordInputSettings) | The new password (see [SRP](https://core.telegram.org/api/srp)) |

## Result

[Bool](https://core.telegram.org/type/Bool)

## Possible errors

| Code | Type                    | Description                                                                                                                                                                                                                                                          |
| :--: | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|  400 | EMAIL\_UNCONFIRMED      | Email unconfirmed                                                                                                                                                                                                                                                    |
|  400 | EMAIL\_UNCONFIRMED\_X   | The provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use [account.verifyEmail](https://core.telegram.org/method/account.verifyEmail) to enter the received verification code and enable the recovery email. |
|  400 | NEW\_SALT\_INVALID      | The new salt is invalid                                                                                                                                                                                                                                              |
|  400 | NEW\_SETTINGS\_INVALID  | The new password settings are invalid                                                                                                                                                                                                                                |
|  400 | PASSWORD\_HASH\_INVALID | The old password hash is invalid                                                                                                                                                                                                                                     |
|  400 | SRP\_ID\_INVALID        | Invalid SRP ID provided                                                                                                                                                                                                                                              |

## Can bots use this methd ?

### yes

## Related pages

### [Two-factor authentication](https://core.telegram.org/api/srp)

How to login to a user's account if they have enabled 2FA, how to change password.

### [account.verifyEmail](https://core.telegram.org/method/account.verifyEmail)

Verify an email address for telegram [passport](https://core.telegram.org/passport).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://painor.gitbook.io/gramjs/working-with-2fa-login/account.updatepasswordsettings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.