account.registerDevice
Register device to receive PUSH notifications
Example
TL schema
Parameters
Name | Type | Description |
flags | Flags, see TL conditional fields | |
no_muted | Avoid receiving (silent and invisible background) notifications. Useful to save battery. | |
token_type | 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| |token|string|Device token| |app_sandbox|Bool|If (boolTrue) is transmitted, a sandbox-certificate will be used during transmission.| |secret|bytes|For FCM and APNS VoIP, optional encryption key used to encrypt push notifications| |other_uids|Vector < int > |List of user identifiers of other users currently using the client|
Result
Possible errors
Code | Type | Description |
400 | TOKEN_INVALID | The provided token is invalid |
Can bots use this methd ?
yes
Related pages
How to subscribe to and handle PUSH notifications
The constructor can be interpreted as a booleantrue value.
Last updated