account.registerDevice

Register device to receive PUSH notifications

boolFalse#bc799737 = Bool;
boolTrue#997275b5 = Bool;
---functions---
account.registerDevice#446c712c token_type:int token:string device_model:string system_version:string app_version:string app_sandbox:Bool lang_code:string = Bool;

Parameters

Name Type Description
flags # Flags, see TL conditional fields
no_muted flags.0?true Avoid receiving (silent and invisible background) notifications. Useful to save battery.
token_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
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<long> List of user identifiers of other users currently using the client

Result

Bool

Possible errors

Code Type Description
400 TOKEN_INVALID The provided token is invalid.
400 WEBPUSH_AUTH_INVALID The specified web push authentication secret is invalid.
400 WEBPUSH_KEY_INVALID The specified web push elliptic curve Diffie-Hellman public key is invalid.
400 WEBPUSH_TOKEN_INVALID The specified web push token is invalid.

Related pages

Handling PUSH-notifications

How to subscribe to and handle PUSH notifications

boolTrue

The constructor can be interpreted as a booleantrue value.

Наверх