invokeWithLayer
invokeWithLayer
Section titled “invokeWithLayer”No description provided by the pinned schema.
Signature
Section titled “Signature”invokeWithLayer#da9b0d0d layer:int query:!X = X;Result type
Section titled “Result type”X
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| layer | int | — | — | No description provided by the pinned schema. |
| query | !X | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import InvokeWithLayerPublic access: miniproto.raw.functions.InvokeWithLayer.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import InvokeWithLayer
# Naming the raw request class is local only; it performs no I/O or network request.request_type = InvokeWithLayerResult family
Section titled “Result family”X (no selected constructor result-family page)
RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | AUTH_BYTES_INVALID | The provided authorization is invalid. |
| 400 | CDN_METHOD_INVALID | You can’t call this method in a CDN DC. |
| 400 | CONNECTION_API_ID_INVALID | The provided API id is invalid. |
| 400 | CONNECTION_LAYER_INVALID | Layer invalid. |
| 400 | INVITE_HASH_EXPIRED | The invite link has expired. |
| 403 | CHAT_WRITE_FORBIDDEN | You can’t write in this chat. |
| 406 | INVITE_HASH_EXPIRED | The invite link has expired. |
Accepted types
Section titled “Accepted types”X (no selected constructor result-family page)
Returned types
Section titled “Returned types”X (no selected constructor result-family page)
Related methods
Section titled “Related methods”initConnection, invokeAfterMsg, invokeAfterMsgs, invokeWithApnsSecret, invokeWithBusinessConnection, invokeWithGooglePlayIntegrity, invokeWithMessagesRange, invokeWithReCaptcha, invokeWithTakeout, invokeWithoutUpdates
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