dataJSON
dataJSON
Section titled “dataJSON”No description provided by the pinned schema.
Signature
Section titled “Signature”dataJSON#7d748d04 data:string = DataJSON;Result type
Section titled “Result type”DataJSON
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| data | string | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.types import DataJSONPublic access: miniproto.raw.types.DataJSON.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.types import DataJSON
# Naming the raw constructor class is local only; it performs no I/O or network request.constructor_type = DataJSONResult family
Section titled “Result family”Relationships
Section titled “Relationships”- Result family:
DataJSON - Accepted by:
bots.answerWebhookJSONQuery,bots.invokeWebViewCustomMethod,bots.sendCustomRequest,help.acceptTermsOfService,messages.requestAppWebView,messages.requestChatJoinWebView,messages.requestMainWebView,messages.requestSimpleWebView,messages.requestWebView,payments.assignPlayMarketTransaction,payments.getPaymentForm,phone.createConferenceCall,phone.joinGroupCall,phone.joinGroupCallPresentation,phone.saveCallDebug,account.passkeyRegistrationOptions,auth.passkeyLoginOptions,help.passportConfig,help.termsOfService,inputBotInlineMessageMediaInvoice,inputMediaInvoice,inputPasskeyResponseLogin,inputPasskeyResponseRegister,inputPaymentCredentials,inputPaymentCredentialsApplePay,inputPaymentCredentialsGooglePay,payments.paymentForm,phoneCall,sendMessageEmojiInteraction,statsGraph,updateBotWebhookJSON,updateBotWebhookJSONQuery,updateGroupCallConnection - Returned by:
bots.invokeWebViewCustomMethod,bots.sendCustomRequest,phone.getCallConfig
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