account.getNotifySettings

account.getNotifySettings

No description provided by the pinned schema.

Signature

account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

Result type

PeerNotifySettings

Parameters

Name	Type	Flag	Default	Description
peer	InputNotifyPeer	—	—	No description provided by the pinned schema.

Python binding

from miniproto.raw.functions import AccountGetNotifySettings

Public access: miniproto.raw.functions.AccountGetNotifySettings.

Safe usage shape

from miniproto.raw.functions import AccountGetNotifySettings

# Naming the raw request class is local only; it performs no I/O or network request.
request_type = AccountGetNotifySettings

Result family

PeerNotifySettings

RPC errors

Code	Error	Description
400	BUSINESS_CONNECTION_NOT_ALLOWED	This method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we’re a user, and users cannot invoke methods over a business connection; (2) we’re a bot, but business mode was disabled in @botfather or (3); we’re a bot, but this method cannot be invoked over a business connection.
400	CHANNEL_INVALID	The provided channel is invalid.
400	CHANNEL_PRIVATE	You haven’t joined this channel/supergroup.
400	PEER_ID_INVALID	The provided peer id is invalid.
401	AUTH_KEY_UNREGISTERED	The specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

Accepted types

InputNotifyPeer Known selected constructors: inputNotifyBroadcasts, inputNotifyChats, inputNotifyCommunity, inputNotifyForumTopic, inputNotifyPeer, inputNotifyUsers

Returned types

PeerNotifySettings Known selected constructors: peerNotifySettings

Related methods

account.getNotifyExceptions, account.updateNotifySettings

Availability evidence

• user only

Provenance

• layer: 228
• structural source: tdlib
• canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
• prose merge precedence: TDLib → Telegram Desktop → Core JSON
• source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 228 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.

Source-diff notes

• tdlib_vs_core: changed_count=68; core_only_count=1; overlap_count=2302; tdlib_only_count=158
• tdlib_vs_tdesktop: changed_count=0; overlap_count=2448; tdesktop_only=null; tdlib_only=accessPointRule, ephemeral.editMessage, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret, updateEphemeralBotCallbackQuery