> 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-notification-settings/account.registerdevice.md).

# account.registerDevice

Register device to receive [PUSH notifications](https://core.telegram.org/api/push-updates)

## 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.registerDevice({
        noMuted: true,
        tokenType: 941000,
        token: 'random string here',
        appSandbox: new Api.Bool({...}),
        secret: Buffer.from('some bytes here'),
        otherUids: [418212],
        }));
    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.registerDevice({
        noMuted: true,
        tokenType: 941000,
        token: 'random string here',
        appSandbox: new Api.Bool({...}),
        secret: Buffer.from('some bytes here'),
        otherUids: [418212],
        }));
    console.log(result); // prints the result
})();
```

{% endtab %}
{% endtabs %}

## TL schema

```
boolFalse#bc799737 = Bool;
boolTrue#997275b5 = Bool;
---functions---
account.registerDevice#68976c6f flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<int> = Bool;
```

## Parameters

|       Name      | Type                                                                                                                              | Description                                                                                             |
| :-------------: | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
|    **flags**    | [#](https://core.telegram.org/type/%23)                                                                                           | Flags, see [TL conditional fields](https://core.telegram.org/mtproto/TL-combinators#conditional-fields) |
|  **no\_muted**  | [flags](https://core.telegram.org/mtproto/TL-combinators#conditional-fields).0?[true](https://core.telegram.org/constructor/true) | Avoid receiving (silent and invisible background) notifications. Useful to save battery.                |
| **token\_type** | [int](https://core.telegram.org/type/int)                                                                                         | Device token type.                                                                                      |

**Possible values**:\
1 - APNS (device token for apple push)\
2 - FCM (firebase token for google firebase)\
3 - MPNS (channel URI for microsoft push)\
4 - Simple push (endpoint for firefox's simple push API)\
5 - Ubuntu phone (token for ubuntu push)\
6 - Blackberry (token for blackberry push)\
7 - Unused\
8 - WNS (windows push)\
9 - APNS VoIP (token for apple push VoIP)\
10 - Web push (web push, see below)\
11 - MPNS VoIP (token for microsoft push VoIP)\
12 - Tizen (token for tizen push)

For 10 web push, the token must be a JSON-encoded object containing the keys described in [PUSH updates](https://core.telegram.org/api/push-updates)| |**token**|[string](https://core.telegram.org/type/string)|Device token| |**app\_sandbox**|[Bool](https://core.telegram.org/type/Bool)|If [(boolTrue)](https://core.telegram.org/constructor/boolTrue) is transmitted, a sandbox-certificate will be used during transmission.| |**secret**|[bytes](https://core.telegram.org/type/bytes)|For FCM and APNS VoIP, optional encryption key used to encrypt push notifications| |**other\_uids**|[Vector](https://core.telegram.org/type/Vector%20t) < [int](https://core.telegram.org/type/int) > |List of user identifiers of other users currently using the client|

## Result

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

## Possible errors

| Code | Type           | Description                   |
| :--: | -------------- | ----------------------------- |
|  400 | TOKEN\_INVALID | The provided token is invalid |

## Can bots use this methd ?

### yes

## Related pages

### [Handling PUSH-notifications](https://core.telegram.org/api/push-updates)

How to subscribe to and handle PUSH notifications

### [boolTrue](https://core.telegram.org/constructor/boolTrue)

The constructor can be interpreted as a **boolean**true value.


---

# 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, and the optional `goal` query parameter:

```
GET https://painor.gitbook.io/gramjs/working-with-notification-settings/account.registerdevice.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.