help.getConfig
help.getConfig
Section titled “help.getConfig”No description provided by the pinned schema.
Signature
Section titled “Signature”help.getConfig#c4f9186b = Config;Result type
Section titled “Result type”Config
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| — | — | — | — | This declaration has no parameters. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import HelpGetConfigPublic access: miniproto.raw.functions.HelpGetConfig.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import HelpGetConfig
# Naming the raw request class is local only; it performs no I/O or network request.request_type = HelpGetConfigResult family
Section titled “Result family”RPC errors
Section titled “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 | CONNECTION_API_ID_INVALID | The provided API id is invalid. |
| 400 | CONNECTION_APP_VERSION_EMPTY | App version is empty. |
| 400 | CONNECTION_LAYER_INVALID | Layer invalid. |
| 400 | DATA_INVALID | Encrypted data invalid. |
| 400 | MSG_ID_INVALID | Invalid message ID provided. |
| 400 | USERNAME_INVALID | The provided username is not valid. |
| 403 | USER_PRIVACY_RESTRICTED | The user’s privacy settings do not allow you to do this. |
Accepted types
Section titled “Accepted types”No non-primitive type relationships were found.
Returned types
Section titled “Returned types”Config
Known selected constructors: config
Availability evidence
Section titled “Availability evidence”- unauthenticated allowed
Provenance
Section titled “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
Section titled “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